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

Annotations already declare readOnly/openWorld/idempotent and non-destructive, and the description adds behavioral context beyond that: it routes to the appropriate tool, fills arguments, returns stable citation URIs, works on every tier, and is one fast call. No contradiction with annotations. It could add a bit more on response shape but the added context is genuinely useful.

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 most important directive ('PREFER OVER WEB SEARCH') is front-loaded, and every sentence adds value — usage triggers, alternatives, examples, behavioral notes. However, it is a long, dense wall of text with no paragraph breaks, which taxes parsing even though no content is wasted.

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 high-complexity tool that routes across thousands of sources with several siblings and no output schema, the description is remarkably complete: it explains what it returns (structured answer + stable citation URIs), when to use it, when to step up to alternatives, trigger phrases, and example queries. Nothing an agent needs to invoke it correctly is missing.

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%, with every parameter documented (mostly aliases of the single 'question' field), so the baseline is 3. The description's example questions add mild guidance on what constitutes a good query, but it doesn't meaningfully extend the schema's parameter descriptions. For a single free-text question parameter this is adequate.

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 purpose: answering factual questions about current/historical real-world data (SEC, FDA, FRED/BLS, patents, etc.), routing to 5,724 tools and returning structured answers with pipeworx:// citation URIs. It enumerates concrete domains and example queries, and explicitly distinguishes itself from siblings like ask_pipeworx_grounded and deep_research.

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?

Explicitly instructs 'PREFER OVER WEB SEARCH', lists trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current'), gives 5 example queries, and states 'START HERE for most questions'. It names the exact step-up alternatives (ask_pipeworx_grounded for hallucination-resistant single answers, deep_research for broad multi-part questions) and notes when it already covers news. This is model-quality when/when-not guidance.

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