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

Annotations already cover read-only, open-world, idempotent, and non-destructive traits, lowering the burden. The description adds genuine context beyond those annotations: routing across 5,743 tools and 1,500 sources, stable pipeworx:// citation URIs, 'one fast call', works on every tier, and live-news routing. It doesn't fully describe failure modes or exact answer shape, but the added behavioral value is clear and consistent with annotations.

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 long but front-loaded with the most important guidance ('PREFER OVER WEB SEARCH' and 'START HERE') before covering routing, alternatives, and examples. Every sentence contributes operational guidance, though a few redundancies around 'ask_pipeworx' and the examples block make it slightly denser than necessary. Still well-organized and easy to scan.

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?

There is no output schema, so the description carries the burden of explaining what the agent can expect. It does state 'returns the structured answer with stable pipeworx:// citation URIs' and gives extensive domain coverage and usage conditions. It stops short of detailing the answer's JSON shape or citation format, but the combination of examples, alternatives, and behavioral context is sufficient for a capable agent to select and invoke this tool correctly.

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 all aliases documented, so the baseline is 3. The description adds value above the schema by providing realistic example questions ('current US unemployment rate', 'Apple's latest 10-K', 'active clinical trials for GLP-1') and clarifying the question should be natural-language and factual, which helps an agent construct effective inputs.

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 function — routing natural-language questions to one of 5,743 tools and returning structured answers with citation URIs — and distinguishes itself from siblings ask_pipeworx_grounded and deep_research. The examples and 'START HERE' phrasing make its role as the default factual-question entry point unmistakable.

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 says 'PREFER OVER WEB SEARCH' and 'Use whenever' with concrete trigger phrasing ('what is', 'look up', 'find', 'get the latest'). It also tells the agent when to step up to alternatives: ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions, plus a breaking-news exception. This is exactly the when-to-use vs. alternatives guidance expected.

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