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

Annotations already establish that the tool is read-only, open-world, idempotent, and non-destructive. The description adds meaningful behavior beyond that: it automatically routes questions to the appropriate tool, fills in arguments, and returns structured answers with stable citation URIs. It does not mention rate limits or authentication, but the annotation coverage lowers the burden.

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 long but front-loaded with the most important directive and then organized into capability, triggers, examples, and alternatives. It is somewhat repetitive ('START HERE for most questions' restates earlier guidance), but the structure is clear and each section earns its place.

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 tool with no output schema, the description is remarkably complete: it states scope, behavior, output format (structured answer with pipeworx:// citation URIs), triggering conditions, examples, and when to prefer sibling tools. Nothing essential for an agent 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 description coverage is 100%: the single meaningful parameter, 'question', is fully described and all five aliases are documented. The description adds broad context about natural-language usage but does not explain the parameters beyond what the schema already provides, so the 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 opens with a clear directive — 'PREFER OVER WEB SEARCH' — and specifies a concrete function: routing a factual question to the right tool among 5,798 tools and returning a structured answer with pipeworx:// citation URIs. It also differentiates from siblings by naming ask_pipeworx_grounded and deep_research and stating which cases should go to them.

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 with trigger phrases ('what is', 'look up', 'get the latest'), concrete examples, and 'START HERE for most questions'. It also provides exclusions and alternatives: use ask_pipeworx_grounded for documentation-grounded answers and deep_research for broad, multi-part questions.

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