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

Annotations already provide readOnly, openWorld, and idempotent hints, but the description adds meaningful context: it routes through a large tool network, returns structured answers with pipeworx:// citation URIs, works on every tier, and is a single fast call. It does not hide the operational nature of the tool. The only minor gap is no explicit mention of failure behavior or rate limits, but annotations carry much of the safety profile.

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 it is front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and every subsequent section earns its place: scope, trigger phrases, examples, escalation criteria, and news behavior. It is somewhat dense and could be tightened, but not at the cost of necessary routing guidance.

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 general-purpose question-answering tool with a simple schema and no output schema, the description is complete: it explains inputs, outputs, alternatives, scope, and behavior. It also preempts common edge cases like breaking-news questions and broad multi-part questions, so an agent has what it needs to invoke the 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?

The schema already documents the `question` parameter and its aliases with 100% coverage, so the baseline is 3. The description goes beyond by explaining what kinds of questions are appropriate, providing concrete example phrasings, and clarifying that the argument is a natural-language request.

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 a routing/answering tool: it takes a natural-language question, routes it across 5,724 tools, and returns a structured answer with citation URIs. It also explicitly distinguishes itself from web search and names sibling tools like ask_pipeworx_grounded and deep_research, so an agent can tell them apart.

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?

This is exemplary: it says to prefer the tool over web search, gives concrete trigger phrases and examples, names exact escalation paths to ask_pipeworx_grounded and deep_research, and even explains when not to escalate because ask_pipeworx already handles news. The agent gets clear when-to-use and when-not-to-use guidance.

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