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

Beyond the annotations (read-only, idempotent, open-world), the description discloses how the tool behaves: it routes to one of 5,767 tools across 1,506 verified sources, fills arguments automatically, and returns structured answers with stable citation URIs. It also states that it provides ground truth from official sources and can cite sources, while warning that it may not be suitable for verbatim/exact-text needs.

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 the key 'prefer over web search' guidance and is dense but purposeful: core behavior, source scope, example queries, and exclusions all appear in a compact span. It loses one point because the middle section is slightly overwrought with repeated trigger phrases and the 'ask_pipeworx ground truth from official source' sentence is grammatically clunky, though still informative.

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?

With no output schema, the description correctly explains the return kind: structured answer with stable citation URIs. It also covers domain scope, source breadth, phrasing triggers, examples, and explicit alternatives. It does not explicitly distinguish ask_pipeworx from sibling variants like ask_pipeworx_grounded or ask_pipeworx_beta, nor from deep_research for broad multi-part questions, so a small completeness gap remains.

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 input schema already documents all six parameters, and they are all aliases for the single 'question' parameter with 100% schema description coverage. The description reinforces the natural-language nature through trigger phrases and examples, but it does not add meaningful parameter semantics beyond what the schema already provides, so the baseline of 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 clear verb-resource pair: it routes a natural-language question to the right internal tool and returns a structured answer with stable pipeworx:// citation URIs. It also lists concrete domains (SEC filings, FDA drug data, FRED/BLS, patents, news, crypto, etc.) and distinguishes itself from web search and search_within without needing to open the schema.

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 says 'Use whenever the user asks...' with explicit trigger phrases and examples, and says 'START HERE for most questions' with clear exceptions: verbatim evidence, verified quotes, single-file exact text, or a direct answer from one specific official source. It also names alternatives like specific source tools and search_within, so an agent can decide when not to call this tool.

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