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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing behavioral details: it routes to one of 5,724 tools across 1,497 sources, fills in arguments automatically, returns structured answers with pipeworx:// citation URIs, and characterizes itself as 'one fast call' that works on every tier. No contradiction 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 every sentence earns its place: the primary directive ('PREFER OVER WEB SEARCH') is front-loaded, followed by trigger phrases, concrete examples, tier/hallucination caveats, and sibling routing. It's efficiently packed for a tool positioned as the default entry point to a 5,724-tool system, though it's slightly verbose compared to the minimal-viable standard.

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 complex router tool with no output schema, the description explains the return contract (structured answer with stable citation URIs), the scope of coverage, and the escalation path to grounded/deep_research variants. It does not detail output shape or error behavior, but the tool's simple single-parameter invocation and rich annotations mean the description covers what an agent needs to call it 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 description coverage is 100% — the schema documents the 'question' parameter with examples and enumerates five aliases (q, text, input, query, prompt), so the schema carries the parameter burden. The description adds contextual value by giving example questions ('current US unemployment rate', 'Apple's latest 10-K') that illustrate the expected input format, but doesn't supply syntax details beyond the schema, so the baseline 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 precise purpose: answer factual questions about real-world entities using authoritative structured data with citations. It enumerates the data domains (SEC filings, FDA data, FRED/BLS, etc.) and explicitly differentiates from siblings like ask_pipeworx_grounded and deep_research, so an agent can select it confidently without inspecting other 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?

The description gives explicit when-to-use guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and a list of trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much'). It also states when to step up to alternatives — ask_pipeworx_grounded for hallucination-resistant single answers, deep_research for multi-part fan-out questions — making the routing decision fully explicit.

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