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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context beyond those: it routes to one of many tools, fills arguments, returns structured answers with stable citation URIs, and works on every tier with one fast call. It does not mention rate limits or error behavior, but for a read-only, idempotent tool the safety profile is already covered.

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 critical decision rule ('PREFER OVER WEB SEARCH') and the data domains. Examples and alternative-tool guidance earn their place for a complex routing tool. Minor redundancy exists between 'even if web search could also answer it' and the opening preference statement, but overall the structure is effective and scannable.

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?

Given the tool's complexity and absence of an output schema, the description adequately explains the return type (structured answer with pipeworx:// citation URIs), the scope (5,724 tools / 1497 sources), the invocation patterns, and the escalation path to siblings. An agent receives enough context to call this tool appropriately without further inference.

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%, so the schema fully documents the six parameter aliases and the required 'question' field. The description does not add parameter-level detail, which is acceptable because the schema is self-sufficient. This meets the baseline but provides no extra semantic value beyond what the schema already includes.

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 clearly identifies the tool as the default entry point for factual questions over authoritative structured data, listing concrete categories (SEC filings, FDA, FRED/BLS, USPTO, etc.) and the routing function across 5,724 tools. It also explicitly distinguishes itself from ask_pipeworx_grounded and deep_research. This goes beyond the mere title and gives an agent a precise operational picture.

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 trigger phrases like 'what is', 'look up', 'find', 'get the latest'. It also tells the agent when to step up to alternatives (grounded for verbatim evidence, deep_research for broad multi-part questions) and even addresses news-breaking coverage. No ambiguity remains about selection.

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