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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses internal routing behavior, argument filling, and the structured output format with pipeworx:// citation URIs. It also adds operational context ('works on every tier, one fast call'). It does not mention failure modes or rate limits, so not a 5, but it is far beyond the annotation baseline.

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 ('PREFER OVER WEB SEARCH') and each sentence contributes either domain coverage, usage triggers, examples, or sibling differentiation. The examples partially repeat the domain list, but the overall density is high and there is no filler.

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?

Even with no output schema, the description states that the return is a structured answer with stable citation URIs, which is enough for an agent to know what to expect. It also covers when to use the tool, when to escalate, and what input formats are accepted. Missing details like error handling or rate limits are minor given the tool's simplicity.

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 fully documented and all aliases listed. The description adds meaningful examples ('current US unemployment rate', 'Apple's latest 10-K') that clarify what kinds of natural-language inputs are acceptable, going slightly beyond the schema's bare alias definitions.

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 ('routes', 'returns', 'fills arguments') and resource ('one of 5,708 tools across 1494 verified sources'), and explicitly positions itself as the default entry point over web search. It also distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by naming their different roles.

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 provides explicit trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') and says 'START HERE for most questions'. It also gives concrete escalation rules: use ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions, while noting breaking news is already covered here.

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