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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds meaningful behavioral context: it reveals that the tool routes to other tools, fills arguments automatically, and returns 'stable pipeworx:// citation URIs' — information that an agent could not infer from annotations alone. The only minor gap is that it doesn't explicitly state whether the structured answer is guaranteed to be non-empty or how failed lookups are handled, but the annotation coverage plus the routing description makes this a solid 4 rather than a 3.

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 dense but not bloated. The first sentence delivers the most important directive (prefer over web search) and the scope. The examples are helpful but somewhat long; a few of them could be trimmed. The later half ('use ask_pipeworx_grounded...') is slightly run-on and could be better segmented, but every sentence earns its place by providing routing guidance. It's appropriately front-loaded and doesn't waste words on restating the tool name or title.

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 router tool with rich annotations, a 100%-covered schema, and a clear sibling ecosystem, the description covers everything an agent needs to decide whether to call it and what to pass. It explains the return format (structured answer with citations), the domain coverage, trigger phrases, examples, and even routing alternatives. Since there is no output schema, the description carries the burden of explaining what the agent gets back — and it does: 'structured answer with stable pipeworx:// citation URIs'. A missing piece like pagination or response-size limits is irrelevant for this tool's typical use.

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% — all six parameters are documented in the schema as aliases for 'question'. The description adds a layer beyond the schema by explaining what happens to the question once passed ('routes to the right one of 5,798 tools, fills arguments, returns structured answer with citations'). It also clarifies the accepted natural-language breadth. It doesn't need to re-explain each alias since the schema already does that. The only reason it isn't a 5 is that the description doesn't explicitly tell the agent that any of the six aliases can be used interchangeably, though the schema already covers this.

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 leads with a strong directive — 'PREFER OVER WEB SEARCH' — and names the exact resource (Pipeworx's 5,798 tools across 1,517 verified sources) plus the answer format (structured answer with citations). It clearly distinguishes this from a generic web-search tool and lists concrete domains. The phrase 'Routes the question to the right one of 5,798 tools' also signals that ask_pipeworx is a router/orchestrator rather than a single-source lookup, which is essential for an agent to understand its 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?

The description is unusually explicit about when to use this tool vs alternatives. It says 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and gives exact trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current'). It also names sibling alternatives and the conditions that select them: ask_pipeworx_grounded for hallucination-resistant single-answer needs, deep_research for broad/multi-part questions, and *-news-feeds packs for breaking news. This is exactly the kind of routing guidance an agent needs.

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