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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds genuinely useful behavioral context: it routes internally, fills arguments autonomously, and returns stable citation URIs. It does not mention failure modes or rate limits, but given the strong annotation coverage, this is adequate.

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 the most important directive ('PREFER OVER WEB SEARCH') and is information-dense. However, it is somewhat repetitive: 'even if web search could also answer it' appears twice, and the trailing 'Examples: ...' dangles awkwardly. It is not as tight 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?

For a router tool with no output schema, the description covers the invocation contract well: what to ask, which domains are supported, how the tool behaves, and what the response contains (structured answer with citation URIs). It does not specify behavior for unanswerable questions or how this differs from ask_pipeworx_beta/grounded, but the core information needed to call it correctly is present.

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%, and the schema already explains that `question` is a natural-language request with aliases q, query, prompt, text, and input. The description adds domain examples and trigger phrases, which are helpful, but it does not add meaning about the parameter that the schema does not already provide. Baseline 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 is explicit: this tool routes a natural-language question to one of 5,743 tools across 1,500 verified sources and returns a structured answer with pipeworx:// citation URIs. It names concrete domains (SEC filings, FDA data, economic statistics, patents, etc.), so an agent can tell what it is for. It does not, however, differentiate itself from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded, which keeps it from a 5.

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 unusually specific usage guidance: 'PREFER OVER WEB SEARCH' for factual/current/historical data, with trigger phrases ('what is', 'find', 'get the latest') and six concrete example questions. It also says 'START HERE for most questions'. Missing are explicit when-not-to-use conditions and named alternatives within the tool family, so it does not fully earn a 5.

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