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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description adds valuable behavior beyond that: it routes the question, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and is described as one fast call. 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 information-dense and well organized, front-loading the most important routing guidance. The 'START HERE' and 'PREFER OVER WEB SEARCH' points are slightly redundant, but every section contributes actionable guidance.

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?

Given no output schema, the description still tells the agent what to expect: a structured answer with citation URIs. It covers selection criteria, alternatives, examples, and the parameter story, so nothing essential for deciding whether and how to invoke the tool 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 coverage is 100%, with the question parameter and its aliases fully documented in the input schema. The description provides example questions but does not add much parameter-level meaning beyond what the schema already gives, so the baseline 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 states a specific verb and resource: it routes questions to one of 6,045 tools and returns structured answers with citation URIs. It clearly distinguishes itself from web search and explicitly names siblings ask_pipeworx_grounded and deep_research, so an agent can tell them apart.

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 triggers such as 'what is', 'look up', 'find', and 'get the latest', plus concrete examples. It also says when not to use it and names the alternatives: ask_pipeworx_grounded for verbatim-evidence 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.