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

The description discloses meaningful internal behavior: it routes the question, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. It also adds important turn-level caveats like 'one fast call per turn' and notes that ask_pipeworx_grounded is the better choice when grounded/precise answers are required. These traits go well beyond the readOnly/openWorld/idempotent annotations and give the agent a realistic model of how the tool behaves.

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 front-loaded with the most important directive ('PREFER OVER WEB SEARCH') followed by scope, examples, and alternatives. Every major section earns its place given the large sibling set and the need to differentiate this router from many other tools. It loses one point because the final breaking-news remark and the 'one fast call per turn' caveat are somewhat awkwardly placed, making the text a bit more sprawling than necessary.

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 complex router tool with no output schema, the description provides everything needed: when to use it, what it does internally, what the return format looks like (structured answer with stable citation URIs), concrete example queries, and clear routing to sibling tools in edge cases. There are no significant gaps that would leave an agent unsure about selecting or invoking the tool.

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?

The input schema already documents the single meaningful parameter and all aliases at 100% coverage, so the baseline is 3. The description adds example queries and clarifies that the argument is a natural-language question, but it does not add substantive semantics beyond what the schema already provides. The examples in the schema itself reinforce this, so no deduction is needed.

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 clearly identifies ask_pipeworx as a general-purpose router that sends natural-language questions to the appropriate tool among thousands of verified sources and returns a structured answer with citation URIs. It sharply distinguishes itself from siblings by positioning itself as the default starting point and explicitly naming alternatives. This is a specific verb+resource definition, not a tautology.

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 gives explicit when-to-use guidance: prefer over web search for authoritative structured data, use for factual lookup triggers like 'what is', 'find', and 'get the latest', and even says to use it even when web search might work. It also names exclusions and alternatives: pipeworx_trending for latest, bet_research for rough counts, entity_profile for profile one-pagers, ask_pipeworx_grounded for grounded answers, and deep_research for broad multi-part questions. No inference is required.

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