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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context: it routes questions, fills arguments automatically, returns structured answers with stable citation URIs, works on every tier, and makes a single fast call. No contradiction with 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?

Although long, the description is densely informative and front-loaded with the most important guidance ('PREFER OVER WEB SEARCH'). Every sentence contributes either usage criteria, scope, examples, or differentiation from sibling tools. No filler or repeated schema content.

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 single-parameter tool with no output schema, the description supplies sufficient context: what kinds of questions to ask, how the tool behaves, what the response includes, and when to consider alternatives. An agent has enough to select and invoke this 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?

Schema coverage is 100% and includes six aliases for the question field, so the schema already documents parameters well. The description adds value by giving concrete example questions and clarifying that the input is a natural-language request, going slightly beyond the schema's minimal alias descriptions.

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 states a clear purpose: it routes factual questions to the appropriate source among 5,721 tools and returns structured answers with pipeworx:// citation URIs. It explicitly differentiates itself from siblings like ask_pipeworx_grounded and deep_research, making the tool's role obvious.

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 gives explicit when-to-use guidance: prefer over web search for factual questions about real-world data, with example phrasings like 'what is', 'look up', and 'find'. It also states when to step up to ask_pipeworx_grounded or deep_research, and covers breaking-news usage.

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