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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive hints. The description adds meaningful behavioral context by explaining that it routes questions, returns structured answers with stable citations, and covers live news. No contradictions exist between the description and 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 longer than average but well-organized, front-loading the core purpose and efficiently differentiating from alternatives. Some redundancy exists (e.g., repeating the list of question types), but it remains clear and scannable, earning a score above the minimum.

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?

Even without an output schema, the description explains the return format: a structured answer with stable pipeworx:// citation URIs. It also describes routing behavior and the scope of data sources. This is sufficient for an agent to understand what the tool does and what to expect from it.

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 6 parameters documented as aliases. The description does not add extra meaning beyond the schema, only reiterates that it accepts query, q, prompt, text, and input as aliases. The baseline of 3 applies since parameters are fully described in the schema.

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 states the tool's purpose: to handle questions about current or historical data across many domains, routing to 5,890 tools from 1,538 verified sources. It distinguishes itself from siblings by explicitly naming ask_pipeworx_grounded and deep_research as alternatives for specific use cases.

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: 'Use whenever the user asks...', 'START HERE for most questions', and 'Step up only when needed' for grounded or deep research. It also clarifies how breaking-news prompts are handled, leaving no ambiguity about when this tool should be selected over its siblings.

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