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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context: it routes to internal tools, fills arguments, returns stable citation URIs, works on every tier, and is a single fast call. It does not contradict 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 dense but every sentence earns its place: it opens with the key override instruction, defines scope, gives concrete examples, states when to escalate, and covers the breaking-news edge case. Examples are illustrative rather than redundant.

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 adequately explains what the caller gets: a structured answer with stable citation URIs. It also covers routing behavior, typical use cases, alternatives, and constraints, making it sufficient for an agent to invoke correctly in most scenarios.

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%, including alias documentation, so the schema carries the main parameter semantics. The description adds helpful usage examples and clarifies that natural-language questions are accepted, but it does not significantly deepen parameter understanding beyond what the schema already provides.

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 that ask_pipeworx routes factual questions to the right tool among 5,724 verified sources and returns structured answers with citation URIs. It differentiates itself from ask_pipeworx_grounded and deep_research by positioning itself as the default, fast entry point.

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?

Explicitly instructs to prefer this over web search for broad factual queries, and gives concrete step-up criteria: use ask_pipeworx_grounded when a hallucination-resistant single answer with verbatim evidence is needed, and deep_research for broad/multi-part fan-out. This leaves little ambiguity about when to choose alternatives.

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