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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context: the tool routes to thousands of underlying tools, fills arguments automatically, and returns answers with stable pipeworx:// citation URIs. It does not mention latency, rate limits, or failure modes, but for a read-only query router this is not a major gap.

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 opening is front-loaded with the key preference and purpose, but the description is bloated with repetition: the same examples and the phrase 'even if web search could also answer it' appear multiple times, and the deep_research guidance is buried after duplicated content. Many sentences do not earn their place, making the definition longer and less clear than needed.

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?

The description covers what the tool does, when to prefer it, example inputs, and the citation-bearing output format. Since there is no output schema, the explicit promise of a 'structured answer with stable pipeworx:// citation URIs' is sufficient for an agent to know what to expect. Annotations cover the safety profile, so the description is complete enough for invocation.

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%: all six parameters are explicitly documented as aliases for the single 'question' parameter. The description adds only illustrative example queries, not additional semantic detail beyond what the schema already provides. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 states a specific verb and resource: it routes natural-language questions to the right one of 5,767 tools across 1,506 verified sources, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. It also enumerates concrete domains and example queries, making it easy to distinguish from web search and from siblings like deep_research.

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 explicitly instructs agents to 'PREFER OVER WEB SEARCH', provides trigger phrases ('what is', 'look up', 'find', 'get the latest', 'current'), and gives a direct alternative: use deep_research for broad/multi-part questions that should fan out across many sources. It also addresses news queries, so an agent knows when this tool is the right choice.

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