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

Annotations already indicate this is read-only, idempotent, open-world, and non-destructive, and the description adds substantial behavior beyond those hints: it routes among 5,743 tools, fills arguments automatically, returns stable pipeworx:// citation URIs, works on every tier, makes one fast call, and handles live news routing. No annotation contradiction exists, and the description enriches the safety/behavior picture meaningfully.

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 the description is long, it is densely packed with actionable guidance: category examples, trigger phrases, alternative-tool routing, tier availability, and answer format. The most important instruction, 'PREFER OVER WEB SEARCH', is front-loaded, and the examples are grouped efficiently. The length is justified by the tool's broad scope.

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 broad routing purpose and the rich annotations/output-less schema, the description covers everything an agent needs: when to use it, when to step up to a sibling, what kind of questions to ask, what the response will contain (structured answer with citation URIs), and operational notes like speed and tier availability. No critical context is missing.

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%, so the schema already documents the single required 'question' parameter and its aliases. The description reinforces the natural-language nature with example queries, but it does not add parameter-level detail beyond what the schema already provides. Baseline 3 is appropriate for high schema coverage.

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 is the default factual question-answering entry point that routes to thousands of verified sources and returns structured answers with citation URIs. It distinguishes itself from ask_pipeworx_grounded and deep_research by naming them and explaining the step-up conditions. This is a specific verb+resource description that an agent can act on immediately.

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 explicitly says to prefer this tool over web search for a broad list of domains and trigger phrases like 'what is', 'look up', and 'get the latest'. It also gives concrete when-not-to-use guidance by directing users to ask_pipeworx_grounded for hallucination-resistant evidence-backed answers and deep_research for broad multi-part questions. This is model usage guidance.

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