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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: it returns citations, fills arguments automatically, works on every tier, and is 'one 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?

The description is long but front-loaded with the most critical directive ('PREFER OVER WEB SEARCH') and maintains structured sections: priority, examples, default behavior, and step-up alternatives. A few phrases ('START HERE', 'default entry point') are mildly redundant, but every sentence contributes actionable 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?

Despite having no output schema, the description explains the return format (structured answer with stable citation URIs), the routing scope, performance expectations, and when to escalate to siblings. For a simple single-question tool with a single required parameter, nothing the agent needs to invoke it correctly 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 description coverage is 100%, and the schema already documents the 'question' parameter plus all aliases with a clear natural-language description. The tool description focuses on usage scenarios and examples rather than parameter-specific syntax, which is acceptable since the schema carries the full parameter burden.

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 names a specific verb (ask/routes), a clear scope (5,743 tools across 1,500 verified sources), and a concrete deliverable (structured answer with stable pipeworx:// citation URIs). It also distinguishes itself from close siblings ask_pipeworx_grounded and deep_research, so an agent can tell them apart without inspecting 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?

It explicitly says 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and lists trigger phrases and examples. It also gives when-not-to-use: use ask_pipeworx_grounded for single hallucination-resistant answers and deep_research for broad/multi-part questions. This is direct routing guidance with named alternatives.

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