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

Annotations already mark readOnly, openWorld, idempotent, and non-destructive. The description adds meaningful behavioral detail: it routes across 5,718 tools, fills arguments, returns 'structured answer with stable pipeworx:// citation URIs,' and is a 'one fast call' on every tier. This goes beyond annotations by informing the agent about routing behavior and output format. No contradiction found.

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?

At roughly 180 words, the description is long, but every sentence carries routing, trigger-phrase, or alternative-tool information. It front-loads the key directive and uses examples efficiently. Slightly overpacked, but not padded or redundant — a 4.

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?

The tool has a single required parameter and no output schema; the description covers when to use it, what it returns (structured answer with citation URIs), how it compares to siblings, and includes multiple concrete examples. Nothing an agent needs to invoke it correctly is missing.

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%; all six parameters are aliases for 'question' and are described in the schema. The description contributes example queries and natural-language trigger phrases, but the schema already documents the parameter semantics. Baseline 3 is appropriate since the description does not add essential parameter meaning beyond the schema.

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 opens with 'PREFER OVER WEB SEARCH...' and defines the specific action: 'Routes the question to the right one of 5,718 tools... returns the structured answer with stable pipeworx:// citation URIs.' This clearly distinguishes it from web search and sibling tools like ask_pipeworx_grounded and deep_research by specifying it as a routing/citation tool.

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?

Explicitly states when to use: 'Use whenever the user asks...' and 'START HERE for most questions — this is the default entry point.' It gives distinct alternatives: 'for a hallucination-resistant single answer... use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research.' No ambiguity about when to choose this tool over siblings.

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