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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral context such as the tool routing to other tools, filling arguments, citing via pipeworx:// URIs, and preferring availability over hallucination, but it doesn't disclose rate limits, latency, or citation format details. Given that annotations carry the safety burden, a 3 is appropriate.

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 information-dense and examples are useful, but it is somewhat long and could be tightened. Front-loading 'PREFER OVER WEB SEARCH' and the tool's purpose is good, but the extensive enumeration of sources and trigger phrases, while valuable, exceeds what can be called concise. Still, every sentence earns its place, so a 4.

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 free-text question-answering tool with one required string parameter, this is complete. It covers when to use it, what it does, how it behaves, and routes to alternatives. The schema already documents the parameter and aliases, and the output is naturally a variable natural-language answer plus citations, so a detailed output schema isn't needed.

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 schema documents the aliases (query, q, prompt, text, input) clearly. The description adds value by describing accepted natural language phrasing and giving concrete example queries, which goes beyond the schema's bare parameter descriptions. However, since it doesn't add any parameters or format constraints beyond the schema, a 4 rather than a 5 is justified.

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'), a resource ('5,767 tools across 1,506 verified sources'), and clearly distinguishes the tool from web search by emphasizing citation-backed structured data. The examples and trigger phrases make it immediately clear what this tool does and how it differs from siblings.

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?

Explicitly tells the agent to prefer this over web search, gives trigger phrases, examples, and states when to use alternatives instead ('deep_research', 'ask_pipeworx_grounded', '*-news-feeds'). This is outstanding when-to-use guidance with concrete alternative routing.

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