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

Annotations already signal read-only, open-world, idempotent behavior, and the description adds useful context: it routes to the appropriate source, fills arguments, returns stable pipeworx:// citation URIs, and works on every tier. It does not describe failure behavior or limitations, but the added detail goes beyond the annotations without contradicting 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 richly informative and front-loaded with the 'prefer over web search' guidance, but it is noticeably long and somewhat repetitive—'START HERE', 'default entry point', and 'use whenever' all convey similar signals. The examples and alternative routing are useful, but the message could be tightened without losing clarity.

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 the absence of an output schema, the description compensates by stating that the result is a structured answer with stable citation URIs. It also covers when to use the tool, what types of questions to ask, and which sibling to step up to. It does not detail response format or edge-case behavior, but for a query-routing tool this is reasonably complete.

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?

The schema already documents all parameters with 100% coverage, including aliases, so the description does not need to explain parameter syntax. The text does add examples of good questions and mentions that aliases are accepted, but that information is already present in the schema. It satisfies the baseline but adds no significant semantic value beyond the structured data.

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 a general factual-question resolver that routes to 5,724 tools and returns structured answers with citations. It also distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by explaining how each differs. The verb 'routes' plus specific resource domains gives agents a precise understanding of the tool's role.

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 explicitly says to prefer this over web search, lists concrete trigger phrases and examples, and names when alternatives should be used: ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions. This is exemplary routing guidance.

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