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

Annotations already mark the tool read-only and idempotent; the description adds meaningful behavioral detail beyond that: it routes to other tools, fills arguments, returns stable citation URIs, works on every tier, and is a single fast call. It also explains the behavior of its escalation alternatives without contradicting the annotations.

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 every segment earns its place: usage precedence, domain list, examples, default-entry-point guidance, and alternatives. It is front-loaded with the most important instruction, though the repeated 'START HERE' and 'use whenever' messages could be tightened slightly.

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?

With no output schema, the description does state what the answer looks like ('structured answer with stable pipeworx:// citation URIs'), covers when to use it, and names alternatives. It stops short of describing error cases or behavior when no source matches, but it is complete enough for an agent to invoke the tool confidently.

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%, so the schema already documents the single meaningful parameter and its aliases. The description adds example questions but no additional constraints on input format, limits, or disambiguation rules, so it stays at the baseline rather than adding parameter-specific value.

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 names a clear action (routes a natural-language question to 5,743 tools across 1,500 sources) and a concrete deliverable (structured answer with pipeworx:// citation URIs). It explicitly distinguishes itself from ask_pipeworx_grounded and deep_research, so an agent can tell them apart without opening other 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?

The description is unusually explicit about when to prefer this tool over web search, what kinds of questions it handles, and when to escalate to ask_pipeworx_grounded or deep_research. It even gives representative example questions and notes that it already covers live-news needs.

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