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

Annotations already mark it read-only, idempotent, and non-destructive; the description adds that the tool fills arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and is a fast single call. It also implicitly discloses limitations by pointing to ask_pipeworx_grounded for hallucination-resistant answers and deep_research for broad fan-out. It does not describe failure or no-match behavior, but the added behavioral context is strong.

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 dense but front-loaded with its most important routing guidance, followed by domains, examples, and step-up alternatives. Each section earns its place given the tool's broad routing scope. It is longer than average, but that length is justified by the need to position this as the default entry point among 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?

With no output schema, the description correctly explains the return shape: structured answer with stable citation URIs. It also covers when to use it, when not to, and what domains it handles. The only notable gap is unsupported-query or error behavior, but the examples and explicit escalation paths make the tool largely self-sufficient.

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%, with question, aliases, and example inputs fully documented. The description's example questions reinforce the natural-language format but do not add meaning beyond what the schema already provides. Baseline 3 is appropriate because the 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 verb (routes) and resource (questions to one of 5,714 tools across 1,495 verified sources), and explicitly frames itself as the default alternative to web search. It also distinguishes itself from siblings ask_pipeworx_grounded and deep_research by use case. This is far beyond a vague or tautological statement.

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?

The description is explicit: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and 'Step up only when needed' with named alternatives and conditions. It even handles the breaking-news edge case by stating ask_pipeworx already routes to live news feeds. This gives an agent clear selection criteria with no inference required.

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