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

Beyond the readOnly/openWorld/idempotent annotations, the description reveals real runtime behavior: it routes to the correct tool, fills arguments, and 'returns the structured answer with stable pipeworx:// citation URIs.' This tells the agent what happens after invocation and what output contract to expect. No contradiction with annotations.

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 instruction ('PREFER OVER WEB SEARCH'), then systematically covers scope, behavior, trigger phrases, and examples. The categories and examples earn their place; there is no padding beyond useful selection signals.

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 complex, routing-style tool with no output schema, the description is complete: it states the question scope, the breadth of sources, the mechanism, and the return format ('structured answer with stable pipeworx:// citation URIs'). An agent has enough information to select and call 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?

The schema already documents the question parameter and its aliases at 100% coverage, so the baseline is 3. The description adds semantic guidance by listing trigger phrases and concrete example questions, which helps the agent shape natural-language input correctly.

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 identifies a fact-answering/resource router: it 'Routes the question to the right one of 5,908 tools across 1540 verified sources' and returns structured answers with citations. However, it does not explicitly differentiate itself from sibling tools such as ask_pipeworx_beta or ask_pipeworx_grounded, so it stops short of a full sibling-distinguishing definition.

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?

It gives explicit when-to-use guidance: 'PREFER OVER WEB SEARCH for questions about current or historical data,' use 'whenever the user asks...' with trigger phrases and examples. It lacks explicit when-not-to-use guidance against sibling research tools, but 'START HERE for most questions' implies a first-line routing role.

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