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

Annotations already provide readOnly/openWorld/idempotent/non-destructive hints. The description adds useful behavioral context: it routes among 5,743 tools, fills arguments, returns structured answers with stable citation URIs, and works on every tier with one fast call. It does not describe failure modes or latency, but the safety profile is well covered by annotations.

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') and immediately explains scope and output. The example list and sibling differentiation are useful, though some phrases are repeated and the text could be tightened without losing value.

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 broad routing tool with no output schema, the description covers what it returns (structured answer with citation URIs), when to use it, when to prefer alternatives, and provides varied examples. It does not mention limitations or fallback behavior, but it gives enough context for an agent to invoke it correctly in most situations.

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%: the schema already documents the main `question` parameter and its aliases. The description contributes examples and query-phrase patterns, but it does not materially enrich the semantic meaning of the parameters beyond what the schema already says, so the baseline score of 3 is appropriate.

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 a specific verb and resource: routes natural-language factual questions to authoritative structured data sources and returns cited answers. It distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research, so an agent can immediately tell what this tool is for.

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?

It explicitly says to prefer this over web search, gives concrete trigger phrases and examples, and states when to step up to ask_pipeworx_grounded or deep_research. It also clarifies that ask_pipeworx already handles news and breaking topics, which prevents unnecessary routing to other tools.

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