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

Beyond the readOnly/idempotent annotations, the description discloses important orchestration behavior: it routes to 5,743 tools, fills arguments, and returns 'the structured answer with stable pipeworx:// citation URIs.' This explains that the tool is a router/aggregator rather than a simple lookup. It doesn't mention failure modes or rate limits, but the added context is meaningful.

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 opening is well-structured and front-loaded, but the description contains a massive, repeated block: the same 'START HERE for most questions...' sentence and example list appears at least eight times verbatim. This creates severe bloat and could confuse an agent parsing the text. It is the opposite of concise.

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?

Despite the repetition, the core description covers the domains, trigger phrases, routing behavior, examples, and return value ('structured answer with stable pipeworx:// citation URIs'). With a single required string parameter and read-only annotations, the agent has enough context to invoke the tool. It could be more complete about output format and limitations, but no output schema exists and the task is simple.

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% — the six parameters (question, q, text, input, query, prompt) are all documented as aliases for the same natural-language question. The description adds example questions and query types, but these don't change or extend parameter meaning beyond what the schema already provides. Baseline 3 applies.

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 the tool's function: 'Routes the question to the right one of 5,743 tools across 1500 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs.' This is a specific Q&A/routing role with a distinct resource. It does not explicitly distinguish itself from sibling tools like ask_pipeworx_beta or deep_research, so it falls short of 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 explicit when-to-use guidance: 'PREFER OVER WEB SEARCH' for listed data domains, 'Use whenever the user asks...' with trigger phrases, and even 'START HERE for most questions — even if web search could also answer it.' It names an alternative (web search) and provides concrete examples, so the selection logic is unmistakable.

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