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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable non-obvious behavior: it routes across thousands of tools, fills arguments automatically, returns citation URIs, and claims one fast call that works on every tier. 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 long but dense and well-structured, front-loading the critical preference directive and usage examples. There is minor repetition between 'Use whenever' and 'START HERE for most questions', but each sentence earns its place by providing routing guidance or examples.

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 meta-routing tool with no output schema, the description covers the answer format, citation behavior, alternative tools, and representative question patterns. It is complete enough for an agent to invoke correctly, though a note about handling unsupported or ambiguous queries would make it stronger.

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% and the schema fully documents the 'question' parameter plus its aliases, so the description does not need to compensate. The examples in the schema and description illustrate usage but do not add meaning beyond what the schema already provides.

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 names a precise verb ('routes the question'), a specific resource ('5,724 tools across 1497 verified sources'), and a concrete output ('structured answer with stable pipeworx:// citation URIs'). It also clearly distinguishes itself from siblings by telling the agent when to use ask_pipeworx_grounded or deep_research instead.

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: 'PREFER OVER WEB SEARCH', 'Use whenever the user asks...', and 'START HERE for most questions'. It also states explicit step-up exclusions for ask_pipeworx_grounded and deep_research, making the routing decision unambiguous.

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