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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering safety and idempotency. The description adds valuable behavioral context: it routes to a large tool set, returns structured answers with stable pipeworx:// citation URIs, and is described as 'one fast call'. These details go beyond annotations without contradicting them. A small gap is lack of failure/error behavior, but annotations carry the safety profile, so a 4 is appropriate.

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 (several sentences) but every part earns its place: it front-loads the core directive ('PREFER OVER WEB SEARCH'), provides domain lists, usage examples, and sibling routing. It could be trimmed slightly (e.g., the list of domains is exhaustive), but the structure is logical and the critical guidance is prominent. It's not tautological or padded, though it is dense.

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?

Given the tool's complexity as a router, the description covers: when to use (most factual questions), what it returns (structured answer with citations), how it works (routes to 5,892 tools), examples, and how to choose among siblings. There is no output schema, but the description explicitly mentions the return format. No missing information that an agent needs to call this tool correctly is evident.

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%: all six parameters are documented in the schema as aliases for 'question'. The description repeats that aliases are accepted ('Accepts query, q, prompt, text, input as aliases'), which adds no new semantic meaning. The description does explain the parameter's role in the context of routing, but since the schema already fully documents the parameters, the baseline of 3 applies – the description adds minimal value beyond the schema.

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: answering factual questions by routing to 5,892 tools across 1,538 sources. It explicitly lists domains (SEC filings, FDA, economic stats, etc.) and differentiates from siblings ask_pipeworx_grounded and deep_research by naming their specific use cases. This is far more than a vague 'answer questions' – it's precise and distinguishes the tool's role.

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?

Provides explicit guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and lists trigger phrases like 'what is', 'look up', 'find'. It also gives concrete alternatives with conditions: use ask_pipeworx_grounded for hallucination-resistant answers, deep_research for multi-part questions, and notes it handles breaking news. This is model guidance with no ambiguity.

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