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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context: it routes to many source tools, fills arguments, returns stable citation URIs, is one fast call, and works on every tier. It does not cover failure modes or rate limits, but that is a minor gap given the annotation coverage.

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 longer than typical but front-loads the core directive and organizes content with clear sections: scope, mechanism, triggers, examples, and escalation. Some redundancy exists ('even if web search could also answer it' and repeated START HERE/step-up guidance), but the structure remains scannable and informative.

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 broad router tool with no output schema, this description covers input expectations, typical use cases, concrete examples, sibling alternatives, and return characteristics (structured answers with citations). Nothing material is missing for an agent to decide when and how to invoke it.

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 documented as aliases for the same natural-language question. The description reinforces the question domain with examples, but adds no syntax or format detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 mechanism: routes the question to one of 5,743 tools, fills arguments, and returns a structured answer with pipeworx:// citation URIs. It also distinguishes itself from siblings by declaring itself the default entry point and explicitly contrasting ask_pipeworx_grounded and deep_research.

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 triggers ('PREFER OVER WEB SEARCH', 'Use whenever the user asks...', 'START HERE for most questions') and explicit step-up conditions for ask_pipeworx_grounded and deep_research. It also addresses the news edge case directly, leaving little room for misrouting.

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