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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description does add genuine behavioral context beyond that: it returns structured answers with stable citation URIs, it self-fills routed arguments, packs scoping silently ignores unknown slugs, and it never returns an empty answer. However, much of the text is promotional framing and trigger-phrase lists rather than behavior, so the signal-to-noise for this dimension is only moderate.

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?

Front-loaded with the highest-value instruction ('PREFER OVER WEB SEARCH'), which is good structure. But it is bloated: the web-search preference is asserted twice, the keyword-trigger list runs long, and a large example set plus a routing paragraph crowd the core message. For a router whose real payload is 'ask a question, get a cited answer', this is longer than necessary.

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?

No output schema exists, yet the description explains what comes back (a structured answer plus stable citation URIs) and how scope failures degrade gracefully. Combined with 100% schema coverage and annotations carrying the safety profile, an agent has enough to invoke and interpret this tool. Minor gap: no latency or cost signal beyond the vague 'one fast call'.

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% and the schema already documents every alias plus a very detailed packs description including the ignored/full_catalog fallback. The description's packs sentence ('answer this using THESE packs'; omit for full-catalog routing) restates what the schema says rather than adding syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource: routes a natural-language question to the right tool among 7,021 across 1850 sources and returns a structured answer with pipeworx:// citation URIs. It explicitly distinguishes itself from siblings ask_pipeworx_grounded and deep_research, so an agent can place it without opening any schema.

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?

Gives an explicit precedence rule ('PREFER OVER WEB SEARCH'), a default-entry-point rule ('START HERE for most questions'), and named alternatives with the conditions that select them (grounded for hallucination-resistant single answers, deep_research for broad multi-part fan-out). This is about as complete a when-to-use/when-not routing statement as exists.

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