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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it routes to internal tools, fills arguments, returns stable pipeworx:// citation URIs, works on every tier, and takes one fast call. It stops short of disclosing possible failure modes or rate limits, but that is not a major gap given the 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 critical 'PREFER OVER WEB SEARCH' directive, followed by a structured breakdown of scope, usage, examples, and fallback tools. Some redundancy exists—the trigger phrases repeat the 'prefer over web search' idea—but every section serves a purpose for a broad meta-tool, and the hierarchy is clear.

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 tool with no output schema, the description compensates by explaining the return format (structured answer with pipeworx:// citation URIs). It covers the full decision space: what questions qualify, what domains are included, when to use siblings, and even how it handles breaking news. An agent has all the information needed 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 six parameters being aliases for the question input. The description adds meaningful semantic guidance through concrete examples ('current US unemployment rate', 'Apple's latest 10-K') and by framing the parameter as a natural-language factual query. This goes beyond the schema's alias explanation.

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 uses a specific verb and resource: routes questions to the right tool among 5,724 tools across 1,497 sources and returns structured answers. It clearly enumerates the covered domains (SEC filings, FDA drug data, FRED/BLS, etc.), and distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as alternatives.

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?

It explicitly says to prefer this tool over web search and gives trigger phrases like 'what is', 'look up', 'find', and 'get the latest'. It also states when to step up to ask_pipeworx_grounded or deep_research, and clarifies that breaking-news questions are still handled here. This gives concrete, non-ambiguous usage direction.

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