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

Annotations already mark the tool readOnly, idempotent, openWorld, and non-destructive. The description adds meaningful behavior beyond annotations: it routes the question across thousands of tools, fills arguments, and returns structured answers with stable citation URIs. It does not discuss latency, errors, or limits, but the caching/routing/citation behavior is useful disclosure for a read-only aggregator.

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 severely repetitive: the same block about domains, routing, trigger phrases, and examples appears at least four times. The first occurrence is front-loaded and useful, but the duplicated text does not earn its place and makes the definition bloated and harder to parse.

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 tool's single required string parameter, readOnly annotations, and lack of an output schema, the description is complete enough for an agent to invoke it correctly. It covers when to use it, what input to provide, what the tool does internally, and what the output will look like with citation URIs.

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%, and the property descriptions already clarify that q, text, input, query, and prompt are aliases for question. The description adds value by enumerating allowed query domains and giving concrete examples such as 'current US unemployment rate' and 'Apple's latest 10-K', which help an agent understand what kind of natural-language input to provide.

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's purpose: it 'Routes the question to the right one of 5,743 tools across 1500 verified sources... returns the structured answer with stable pipeworx:// citation URIs.' This is a specific router/Q&A tool with a well-defined resource. It does not explicitly distinguish itself from sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded, so it misses the top-tier sibling differentiation bar.

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', trigger phrases like 'what is', 'look up', 'get the latest', and concrete examples. It also says 'START HERE for most questions.' However, it does not state when not to use this tool or when to prefer sibling variants such as ask_pipeworx_beta or deep_research.

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