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

The description adds meaningful behavioral detail beyond the readOnly/openWorld/idempotent annotations: it reveals dynamic routing, automatic argument filling, and stable pipeworx:// citation URIs in the response. It does not address edge cases like no-results handling, latency, or auth, but for a read-only query tool the disclosed behavior is strong.

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 front-loaded with 'PREFER OVER WEB SEARCH' and organized around usage signals, examples, and a closing start-here directive. It earns its length but repeats 'even if web search could answer it' twice, which makes it slightly redundant.

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?

Without an output schema, the description adequately explains the return shape by mentioning structured answers and stable citation URIs. It also covers routing behavior and broad query categories; the main omission is guidance for choosing between this and the ask_pipeworx_beta/grounded siblings.

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%, including the six aliases for the single required parameter, so the structured data already fully documents the parameters. The description contributes only natural-language usage examples (e.g., 'current US unemployment rate') rather than new parameter-level semantics.

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 specific action ('routes the question to the right tool'), a specific resource domain (5,908 tools across 1,540 verified sources), and an output (structured answer with citation URIs). It clearly differentiates from web search, but it does not explain how it differs from sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded.

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?

It explicitly says 'PREFER OVER WEB SEARCH' and gives concrete triggers ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') plus examples. It presents this tool as the default catch-all, but it never states when to prefer the sibling ask_pipeworx variants or deep_research instead.

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