Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint/openWorldHint/idempotentHint annotations, the description discloses account requirements, parallel execution, gap[] reporting for unanswered facets, contradictions[] for disagreeing findings, citation_uri fetchability guarantees, semantic excerpting, and realistic latency ranges. This is rich behavioral context well beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence carries distinct operational information: auth requirements, fit criterion, non-open-web nature, return shape, citation semantics, depth semantics, and timing. It is appropriately dense for a complex research tool, though the depth-related behavior is partially restated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even without an output schema, the description tells the agent what to expect: findings with verbatim evidence, confidence, source, fetched_at, citation URI, gaps[], contradictions[], and hop field. It also covers latency expectations and auth prerequisites, making the tool safe to invoke under virtually all conditions an agent could encounter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds genuine value by explaining the behavioral consequences of each depth value: quick is single-hop, standard adds gap recovery and contradictions[], and thorough chases leads and recovers gaps. It also clarifies that the question parameter is meant for broad or multi-part natural-language queries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('research'), a specific resource (Pipeworx's 1506 structured data sources), and a clear mechanism (facets, parallel routing, findings packet). It explicitly contrasts itself with open-web search and with ask_pipeworx, so an agent can distinguish it from siblings without inspecting their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditions: if not signed in, use ask_pipeworx; for a single lookup, use ask_pipeworx; for broad/multi-part structured-data questions, use this tool. It also explains when the paid tier applies and how depth levels change behavior, leaving no ambiguity about when to select this tool over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.