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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses key runtime behavior: it is an orchestrator that routes to other tools, fills arguments automatically, and returns stable pipeworx:// citation URIs. It also notes that it works even where web search would also answer, and contrasts the grounded variant's stricter citation behavior. 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 core directive and organized into purpose, examples, and fallback guidance. There is some redundancy around web-search comparison, but every section earns its place in helping an agent select and invoke the tool.

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 complex router tool with no output schema, the description is unusually complete: it covers input scope, examples, output format (structured answer with citation URIs), and sibling routing. It does not mention failure/error behavior or rate limits, but those are less critical given the rich annotations and the explicit fallback to web search.

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 description coverage is 100%, so the schema already documents all parameters. The description reinforces that the parameter is a natural-language question through examples, but adds no new parameter-level meaning beyond the schema's alias explanation. Baseline 3 applies.

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 verb and resource: it routes a natural-language question to one of 5,743 tools across 1,500 verified sources, fills arguments, and returns a structured answer with citation URIs. It clearly distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by naming them as alternatives.

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 data, and lists triggered phrases ('what is', 'look up', 'find', 'current', etc.) plus concrete examples. It also states exclusions: use web search for non-factual or creative questions, deep_research/bet_research for multi-step analysis, and ask_pipeworx_grounded when verification with explicit citations is needed.

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