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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds valuable behavioral context: internal routing across 5,743 tools, argument filling, stable citation URIs in the response, and 'one fast call' performance. It does not contradict annotations and goes beyond what they communicate.

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 structured and front-loaded: it starts with the key directive, then lists covered domains, behavior, trigger phrases, examples, and sibling routing. With minor redundancy ('START HERE' and 'default entry point' overlap), nearly every sentence earns its place given the need to differentiate from many siblings.

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 one-parameter tool with rich annotations and no output schema, the description covers the essential ground: scope, domain list, trigger phrases, examples, alternatives, and what the response will contain (structured answer with citations). Gaps like error handling or rate limits are minor and not critical for correct invocation.

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% — all six parameters are aliases of 'question' and are fully described in the schema. The description reinforces semantics with usage triggers and examples, but it does not add parameter-specific details beyond the schema, so baseline 3 applies.

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 the tool's function: routing natural-language questions to 'the right one of 5,743 tools across 1500 verified sources' and returning structured answers with pipeworx:// citation URIs. It explicitly differentiates from siblings by naming 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?

It gives explicit when-to-use guidance ('PREFER OVER WEB SEARCH', 'START HERE for most questions') and when-not-to-use/alternative guidance ('for a hallucination-resistant single answer ... use ask_pipeworx_grounded; for a broad/multi-part question ... use deep_research'). Also lists trigger phrases and concrete examples, leaving no inference required.

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