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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses that the tool routes to one of thousands of source tools, fills in arguments automatically, and returns structured answers with stable citation URIs. These are behavioral details not present in the annotations. No contradiction with the annotations was found.

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 text is long but front-loaded with the most important directive, followed by behavior, usage triggers, examples, and sibling routing. No obvious filler sentences, and the length is justified by the routing complexity; it just stops short of being maximally concise because of the extended category list and examples.

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 no-output-schema router with many siblings, the description is complete: it names the data domains, gives concrete query examples, describes the output format (structured answer with citations), and routes the main exceptions to specific sibling tools. An agent has enough context to select ask_pipeworx correctly without further documentation.

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 documented as aliases for the natural-language question. The description reinforces what the question should contain ('current US unemployment rate', 'Apple's latest 10-K') but does not add semantic information about the parameters beyond the schema's own descriptions, so the 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 opens with 'PREFER OVER WEB SEARCH' and states a specific function: routing a natural-language question to the right one of 5,798 tools across 1,517 verified sources and returning structured answers with pipeworx:// citation URIs. It also differentiates from sibling tools by naming the alternatives (ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) for cases where this tool is not appropriate.

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?

Gives explicit when-to-use triggers ('what is', 'look up', 'find', 'get the latest', 'how much', 'current', or any factual question about real-world entities...') and says to prefer it over web search even when web search could answer. It lists specific exclusion conditions such as hypothetical questions, grounded/reasoning-heavy queries, and broad multi-part research, naming the correct sibling for each.

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