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

Annotations already signal read-only, idempotent, open-world, non-destructive behavior. The description adds meaningful behavioral context: it routes across 5,798 tools, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, requires no setup, and is intended as a single-call entry point. This goes beyond the annotation hints, though it still leaves some response-format details implied rather than fully specified.

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 front-loaded with its most important guidance and is information-dense, but it becomes sprawling: a long domain list, trigger phrases, examples, and a disjointed closing section about step-up alternatives. Most content earns its place, but the structure feels cluttered and a bit rambling rather than crisp.

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?

For a one-required-parameter routing tool with rich annotations, the description is largely complete: it explains when to use it, what it returns, what categories of questions it handles, and when to escalate to siblings. The lack of an output schema is partly mitigated by the explicit mention of structured answers and citation URIs, though exact response shape is not described.

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 description coverage is 100%, and the schema documents `question` and its aliases clearly. The description does not add much parameter-level meaning beyond saying the tool accepts natural-language questions, which the schema already states. This matches the baseline for high schema coverage.

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?

The description states a clear purpose: ask natural-language questions and get authoritative structured answers from a large tool/source network instead of web search. It lists covered domains and example queries, and it differentiates itself from web search and sibling research tools. The verb and resource are specific enough that an agent can distinguish this from siblings like deep_research or ask_pipeworx_grounded.

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?

The description explicitly says to prefer this over web search for factual questions and even lists trigger phrases like 'look up', 'find', and 'get the latest'. It also names alternatives: ask_pipeworx_grounded for citation-grounded answers and deep_research for broad/multi-part questions. This gives an agent clear routing conditions with explicit exclusions.

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