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

Annotations already establish a safe profile (readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely non-obvious behavioral context: it is an orchestrator that routes to 5,798 sub-tools, auto-fills arguments, and returns stable pipeworx:// citation URIs — none of which is inferable from the annotations. No contradiction with the read-only/idempotent hints.

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?

Well front-loaded: the most important instruction ('PREFER OVER WEB SEARCH') leads, followed by scope, mechanics, triggers, examples, and routing alternatives in logical order. Nearly every sentence earns its place, but a garbled fragment ('default entry point, works on every tier, one fast call. Step up only when needed:') reads like concatenated bullet points, and the example list is slightly long.

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 router over thousands of sources, the description is unusually complete: it covers purpose, domain scope, trigger phrasing, sibling routing, and — important since there is no output schema — the return shape (structured answer with citation URIs). Remaining gaps are minor: no failure modes or known limitations, and the tier/latency claim is garbled. Annotations carry the safety profile, so nothing critical blocks correct invocation.

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% and the question parameter is fully documented with its five aliases, so the baseline is 3. The description adds value by specifying what kinds of questions to pass — trigger phrases plus six concrete examples ('current US unemployment rate', 'Apple's latest 10-K', 'adverse events for ozempic') — which goes beyond the schema's generic 'Your question or request in natural language'.

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?

States a specific function: routes natural-language questions to the right one of 5,798 tools across 1,517 verified sources, fills arguments, and returns structured answers with pipeworx:// citation URIs. It explicitly differentiates from siblings by naming ask_pipeworx_grounded and deep_research as alternatives for narrower/broader needs, so an agent can tell them apart without opening their schemas.

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?

Opens with an explicit priority rule ('PREFER OVER WEB SEARCH'), enumerates covered domains (SEC, FDA, FRED/BLS, USPTO, ATTOM, news, clinical trials, etc.), lists trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current'), and explicitly says to use it 'even if web search could also answer it'. It closes with named alternatives and the conditions that select them: single citation-grounded answer → ask_pipeworx_grounded; broad/multi-part fan-out → deep_research.

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