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

The description adds valuable behavioral context beyond the annotations by explaining that this is a routing/orchestration tool that automatically fills arguments and returns answers with stable pipeworx:// citation URIs. This is useful and consistent with the readOnlyHint, openWorldHint, idempotentHint, and destructiveHint annotations. It does not disclose potential latency, authentication requirements, or failure modes, but the annotations already cover the safety profile reasonably well.

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 substantially overlong and repetitive. The 'START HERE for most questions — even if web search could also answer it. Examples:' sentence and the entire example list are duplicated almost verbatim. While the content is mostly relevant, the redundancy and run-on style make it less concise than it should 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?

For a broad question-routing tool with no output schema, the description covers the key contextual needs: what the tool does, when to use it, what kinds of questions it accepts, what sources it draws from, and what the response includes. It is slightly incomplete in not naming exclusions or explicitly differentiating from sibling variants, but overall the agent has enough context to invoke it correctly.

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%, so the schema already fully documents the 'question' parameter and its aliases. The description adds example queries and trigger phrases, which is helpful, but it does not meaningfully extend the parameter semantics beyond what the schema and its examples already provide. This stays at the high-coverage baseline of 3.

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 what the tool does: it routes a natural-language question to one of 5,798 tools across 1,517 verified sources, fills arguments, and returns a structured answer with citation URIs. This is a specific verb+resource statement and effectively differentiates from web search, but it does not explicitly distinguish the tool from closely related siblings like ask_pipeworx_beta, ask_pipeworx_grounded, or deep_research.

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 strong when-to-use guidance, including trigger phrases ('what is', 'look up', 'get the latest', 'current'), a broad list of domains, and an explicit directive to prefer this tool over web search. However, it does not provide when-not-to-use conditions or name sibling alternatives, so the routing guidance is clear but not exhaustive.

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