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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses useful behavior: it routes to thousands of source tools, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. It does not cover failure modes or speed, but the annotations already cover the mutation and world-access profile.

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 key guidance is front-loaded, but the description repeats the same 'Use whenever... Examples... START HERE' passage multiple times and ends with an unrelated instruction to 'Reset all context...'. This padding makes the description significantly less concise and structured.

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 broad routing tool, the description covers what it does, when to use it, example queries, and the form of the response (structured answer with citation URIs). The repetitive tail and lack of explicit unsupported-question types are gaps, but the essential selection and invocation information is present.

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?

The schema already documents all six parameters with 100% coverage, and most are aliases for the same natural-language question. The description adds no parameter-level guidance beyond what the schema provides, so it meets the baseline but does not exceed it.

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 the tool's action: it routes factual questions to relevant tools and returns structured answers with citations. It is specific about scope ('current or historical data', SEC, FDA, FRED/BLS, etc.). However, it does not explicitly distinguish itself 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?

The description gives strong when-to-use guidance, including trigger phrases, examples, and explicit guidance to prefer this over web search ('even if web search could also answer it'). It lacks clear when-not-to-use guidance and does not mention alternatives among sibling ask_pipeworx variants, so it is not quite a 5.

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