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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds meaningful behavior: it routes, fills arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and is a single fast call. No contradiction with 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 front-loaded with the key directive ('PREFER OVER WEB SEARCH') and then organizes guidance into when-to-use, examples, and escalation paths. Some repetition exists around what counts as a factual question, but the examples and routing hierarchy earn their place.

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 high-complexity router tool with no output schema, the description covers the return shape (structured answer with citation URIs), default entry-point status, tier availability, performance expectation, and clear escalation criteria. Nothing an agent needs to decide whether and how to call it is missing.

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%: the only real parameter, question, is fully described and all aliases are documented. The description adds example queries and trigger phrases, but it does not need to explain parameter semantics further because the schema already carries the full burden. Baseline 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 states a specific role: route factual questions to the right tool among 5,801 tools and return structured answers with citations. It clearly distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as alternatives, so an agent knows this is the default broad-routing entry point rather than the grounded or fan-out variants.

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?

Usage guidance is explicit and actionable: prefer this over web search, use it whenever the user asks 'what is', 'look up', 'find', etc., and step up to alternatives only when needed. It names the exact conditions for ask_pipeworx_grounded and deep_research, leaving no ambiguity about when to choose each sibling.

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