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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds useful behavioral detail: it routes to 5,724 tools, fills arguments, returns structured answers with stable pipeworx:// citation URIs, and works across all tiers with one fast call. It does not fully disclose failure modes or response-shape edge cases, but the added context exceeds what annotations alone provide.

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 it is front-loaded with the most important routing directive and organized into preference, rationale, examples, and escalation paths. Some repetition exists between 'PREFER OVER WEB SEARCH' and 'START HERE', and the domain list is extensive, but most sentences add selection-relevant value. It earns a 4 rather than 5 because it is slightly over-wordy.

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?

There is no output schema, so the description must explain what the agent gets back, and it does: a structured answer with stable citation URIs. It also covers scope, trigger phrases, examples, sibling escalation paths, tier behavior, and adaptability to breaking news. For a high-complexity default router, this is complete enough for an agent to select and invoke it correctly.

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 main 'question' parameter and all aliases documented in the schema itself. The description contributes little to parameter semantics except reinforcing that the input is a natural-language question. Baseline 3 is appropriate because the schema already carries the full parameter burden.

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 a user's factual question to the right tool among 5,724 verified sources and returns a structured answer with citation URIs. It strongly distinguishes itself from web search and from siblings like ask_pipeworx_grounded and deep_research. The examples reinforce the scope without ambiguity.

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 gives explicit when-to-use guidance: prefer over web search for factual/current/historical questions, use as the start-here default, and 'step up only when needed' to grounded or deep_research. It also provides concrete triggers like 'what is', 'look up', 'get the latest', and example queries. This is unusually actionable routing guidance.

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