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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds meaningful behavioral context by disclosing that the tool selects among 5,798 tools, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. It does not discuss failure or ambiguous-query behavior, but it enriches what the annotations already imply.

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 guidance ('PREFER OVER WEB SEARCH') and packs domain scope, mechanism, triggers, and examples into a focused statement. It is slightly repetitive between 'PREFER OVER' and 'START HERE', but every sentence adds operational value.

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 single-required-parameter, read-only router with no output schema, the description covers what the tool does, when to use it, what kinds of questions it accepts, and what the response includes (structured answer with citations). It could address out-of-scope or failed-query behavior, but nothing essential to a correct call 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 description coverage is 100%, so the question parameter and its aliases are already fully documented in the schema. The description adds useful examples and domain scope, but it does not explain parameter semantics, alias behavior, or formatting beyond what the schema provides; 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 clearly identifies the tool as the preferred route for factual, current, and historical data questions, and explains that it routes to thousands of verified sources and returns structured answers. It differentiates itself from web search, but does not explicitly distinguish itself from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded, so it misses the top score.

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 provides concrete trigger phrases, example questions, and explicit guidance to prefer this tool over web search and to start here for most questions. It does not, however, state when not to use it or mention relevant alternatives such as deep_research or search, so exclusion guidance is missing.

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