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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses that the tool routes to 5,724 tools, fills arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and is a single fast call. It does not fully describe failure modes or the absence of verbatim-evidence guarantees in the base tool, though it implies this by recommending ask_pipeworx_grounded for that need.

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 section earns its place: the 'PREFER OVER WEB SEARCH' directive is front-loaded, followed by capability, examples, and escalation guidance. The list of domains and example queries is somewhat extensive, but it prevents misrouting and clarifies scope; no filler or tautology.

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 there is no output schema, the description does enough by describing the structured-answer format with citation URIs, naming usage triggers, and providing examples. It also covers tier availability and explicitly routes edge cases like breaking news and multi-part research to the correct sibling. Minor gaps remain around possible failure modes and the base tool's hallucination profile, but these are partially addressed by the grounded alternative.

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 for the six parameters is 100%, with the question parameter already explaining aliases. The description adds meaningful query-construction guidance through trigger phrases and concrete examples such as 'current US unemployment rate' and 'patents Tesla was granted last month', which helps an agent formulate effective natural-language questions.

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 this as a router/default entry point for factual and real-world questions, with explicit domain coverage from SEC filings to sports. It distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as escalation paths rather than alternatives for the same task.

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 provides explicit when-to-use guidance ('START HERE for most questions'), enumerates trigger phrases like 'get the latest' and 'how much', and states when not to use it ('Step up only when needed') with specific sibling alternatives. It even addresses breaking news and clarifies that live news is already handled by this tool.

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