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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond annotations: routing behavior, argument filling, stable citation URIs, a shared 95k call quota, and the absence of a code execution tool. However, the trailing 'STUB.' is an unexplained artifact that prevents a perfect score.

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 ('PREFER OVER WEB SEARCH') and includes many useful details. However, it is quite long, packs numerous alternative tool names into dense paragraph flow, and ends with an unexplained 'STUB.' marker. Every sentence mostly earns its place, but the structure is not as clean as it could be.

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 there is no output schema, the description covers the return value well: 'structured answer with stable pipeworx:// citation URIs'. It also provides domains, examples, quota limits, and sibling-tool routes, which makes the tool actionable. A minor gap is that failure/error behavior and the meaning of the 'STUB.' marker are not explained.

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 schema already covers all six parameters at 100% — they are all aliases for the same free-text question. The description adds substantial meaning beyond the schema by explaining what kinds of questions to ask, providing rich examples, and listing trigger phrases. It does not repeat schema details but instead clarifies the intended input semantics.

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 states that ask_pipeworx routes questions to one of 5,798 tools across 1,517 verified sources and returns structured answers with pipeworx:// citation URIs. It names specific data domains and gives concrete example queries, which distinguish it from vague 'ask a question' tools. It also explicitly contrasts itself with sibling tools like deep_research and 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 gives explicit when-to-use guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and trigger phrases like 'what is', 'look up', 'find', and 'get the latest'. It also names alternatives for specific cases: ask_pipeworx_grounded for citation follow-ups, deep_research for multi-angle research, bet_research/polymarket_* for breaking news, and discover_tools for capabilities. This is unusually strong routing guidance.

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