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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the bar for additional context is lower. The description adds meaningful behavioral detail: it routes questions internally, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and is a single fast call. It does not discuss failure modes or rate limits, but it goes well beyond the annotation baseline.

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 the length is justified by the tool's role as a default router: it packs domains, trigger phrases, examples, sibling routing guidance, and limitations into a front-loaded structure. A little redundancy exists across the trigger-phrase list and examples, so it is not maximally tight.

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, no output schema, and many siblings, the description is remarkably complete: it explains what the tool does, when to use it, when not to use it, what alternatives exist, and what the return shape looks like (structured answer with citation URIs). It does not cover edge cases like no-result behavior or cost/latency tradeoffs, but the essential call-and-routing context is present.

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% and all six parameters are documented aliases for 'question', so the schema already carries the parameter meaning. The description reinforces the question-oriented nature with examples, but adds no substantive semantics beyond 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 opens with a clear directive to prefer this tool over web search and names its specific job: routing questions to one of 5,724 tools across 1,497 verified sources and returning structured answers with citations. It distinguishes itself from siblings like ask_pipeworx_grounded and deep_research without requiring the agent to open their 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?

Usage guidance is explicit and actionable: it lists covered data domains, trigger phrases like 'look up' and 'get the latest', concrete examples, and a hierarchy for stepping up to ask_pipeworx_grounded or deep_research. It also explicitly covers the breaking-news case and names the sibling tools as alternatives.

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