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

The description adds useful behavioral context beyond the annotations: it discloses that the tool dynamically routes to the right sub-tool, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. Annotations already cover read-only, open-world, and idempotent behavior, and the description does not contradict them.

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 selection signal ('PREFER OVER WEB SEARCH') and uses compact, illustrative examples. It is somewhat long due to the domain list and repeated web-search emphasis, but each section supports tool selection without significant waste.

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 parameter-light router with rich annotations and no output schema, the description covers input format, output behavior (structured answer with citation URIs), scope, and usage triggers. An agent has enough information to invoke it correctly without missing critical details.

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%, with all six parameters documented as aliases for the single 'question' parameter. The description contributes example questions and trigger phrases but adds no new parameter-level meaning, so the baseline score of 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 states the tool's function: it routes natural-language factual questions to one of 5,743 tools across 1,500 sources and returns structured answers with citations. It distinguishes the tool from web search, but it does not explicitly differentiate it from sibling tools such as ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, or query.

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 strong when-to-use guidance: prefer over web search for current or historical data, with specific trigger phrases and examples. However, it lacks explicit when-not-to-use guidance or references to alternative sibling tools, so it stops short of a 5.

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