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

Annotations already declare this a safe, read-only, idempotent operation, and the description adds genuinely useful behavioral context: it fills arguments automatically, returns a structured answer with stable pipeworx:// citation URIs, works on every tier, and is a single fast call. It does not overpromise output details, which is acceptable given no output schema exists. Minor gap: it does not mention rate limits or specific failure behavior, but the annotation safety profile reduces that burden.

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 average, but it is justified: the tool has a broad routing scope, a long domain list, and multiple sibling tools to disambiguate. It is front-loaded with the most important directive ('PREFER OVER WEB SEARCH') and uses sectioned escalation guidance. A few phrases are redundant ('START HERE' plus 'default entry point'), so it is not a perfect 5, but every sentence 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 zero-output-schema tool with very broad scope, the description tells the agent what to expect: a structured answer with citation URIs, a fast single call, and availability on every tier. It also covers when to escalate to grounded or deep_research variants, and gives representative example queries for common domains. Nothing essential for invoking this 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 coverage is 100%: all six parameters are documented as aliases for 'question', and the schema already explains that it accepts query, q, prompt, text, and input. The description adds no parameter-level semantics beyond what the schema provides, but it does provide rich example questions in the schema's examples array. Baseline 3 is appropriate because the schema carries the parameter documentation weight.

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-resource pair—'Routes the question to the right one of 5,743 tools' and 'returns the structured answer'—and gives a crisp contrast with siblings: ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad multi-part questions. The examples and domain list make the scope unmistakable. It clearly distinguishes itself from both generic web search and nearby tools.

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?

Usage guidance is explicit and prioritized: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and 'Step up only when needed' with named alternatives and their exact conditions. It even handles the 'breaking news' edge case, telling the agent that ask_pipeworx already routes to live news feeds. This leaves little inference burden on the agent.

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