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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds non-obvious behavior: routing across 5,743 tools, argument filling, stable pipeworx:// citation URIs, one fast call, and live-news coverage. It does not go into error or rate-limit behavior, but that is minor for this read-only retriever.

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?

Information is front-loaded with the most important directive first, then scope, examples, default stance, and escalation paths. The long domain list is justified by the wide scope, and no sentence is pure 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?

For a central retrieval tool with no output schema, the description covers scope, output format (structured answer with citation URIs), when to use it, when to escalate to grounded or deep_research, and how it handles breaking news. This is sufficient for an agent to decide whether to call it and what to pass.

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?

Input schema already documents all six aliases at 100% coverage, so the baseline is 3. The description does not add parameter-level syntax beyond what the schema provides, though its example questions and 'natural language' framing reinforce expected usage.

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?

States explicitly that it routes natural-language questions to one of 5,743 tools across 1,500 sources and returns structured, cited answers; the scope (current/historical real-world data) and examples make the verb/resource clear. It also explicitly separates itself from ask_pipeworx_grounded and deep_research, so an agent can tell them apart without inspecting schemas.

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?

Gives strong positive guidance ('PREFER OVER WEB SEARCH', 'START HERE for most questions—default entry point') and explicit escalation rules ('Step up only when needed: ... use ask_pipeworx_grounded; ... use deep_research'). It lists trigger phrasing and covers the case where web search could also answer, removing ambiguity about when to call this tool.

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