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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context: it routes across 5,767 tools, fills arguments, returns citations, works on every tier, and handles live news. This exceeds what the annotations alone provide.

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 every sentence earns its place: the main directive is front-loaded, examples are compact and relevant, and alternative routing is compressed into a single actionable block. No wasted words or repetition of 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 complex router tool with no output schema, the description is remarkably complete: it explains the tool's scope, the types of questions it handles, example inputs, the output format (structured answer with pipeworx:// citation URIs), tier availability, and exactly when to prefer siblings. Nothing an 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 coverage is 100% and all six parameters are aliases of 'question', so the schema already documents the parameter. The description adds value by supplying concrete example questions and a decision rule for when a query qualifies, which helps an agent construct an appropriate value.

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 specific action and resource: it routes questions to the right one of 5,767 tools and returns structured answers with citation URIs. It clearly differentiates itself from siblings like ask_pipeworx_grounded and deep_research by describing its role as the default entry point.

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?

Explicitly says 'PREFER OVER WEB SEARCH' and 'START HERE for most questions', then names the exact conditions for stepping up to ask_pipeworx_grounded ('hallucination-resistant single answer with verbatim evidence + confidence') and deep_research ('broad/multi-part question'). This is textbook when-to-use guidance.

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