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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond the schema: that the tool routes to thousands of internal tools, automatically fills arguments, and returns stable citation URIs. It does not discuss limitations like latency, failure modes, or domain coverage gaps, which keeps this from a 5.

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 front-loaded with the most important directive and covers a lot of ground in a compact but dense form: domain list, trigger phrases, examples, and sibling routing. It is slightly repetitive ('PREFER OVER WEB SEARCH', 'Use whenever...', 'START HERE for most questions' all say similar things), but the repetition is arguably useful emphasis for a broad router tool. Every major section earns its place.

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 high-complexity router with no output schema and many sibling tools, this is complete: it states the return behavior (structured answer with citation URIs), gives concrete input examples, covers when to use it, and routes to alternative tools for cases that should not use it. Nothing essential to selecting or calling the tool 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%: the question parameter and all aliases are already documented, and the schema includes worked examples. The description reinforces natural-language input with example questions, but it does not need to add parameter-level semantics. The baseline of 3 is appropriate because the structured schema carries the parameter documentation 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 routing behavior: it sends the question to one of 5,798 tools across 1,517 verified sources and returns a structured answer with pipeworx:// citation URIs. It is clearly distinguished from sibling tools by the opening directive 'PREFER OVER WEB SEARCH' and by explicit alternative routing to ask_pipeworx_grounded, entity_profile, 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 criteria ('Use whenever the user asks...'), domain lists, and trigger phrases, and it says to prefer this over web search even when web search could answer. It also names the specific alternatives for grounded single-fact questions, entity profiles, and deep/open-ended research, so an agent can select between siblings without guessing.

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