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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context beyond those: it routes questions to 5,798 tools across 1,517 sources, fills arguments automatically, and returns stable pipeworx:// citation URIs. This is strong context, though it does not go into failure modes or confidence behavior.

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 long but front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and earns its length with domain lists, examples, and alternative-tool routing. It could be tightened slightly, but each major sentence adds distinct value for a broad meta-tool.

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 question-routing tool with no output schema, the description covers what it does, which domains it handles, how answers are cited, when to prefer it, and when to use alternatives. An agent has enough context to invoke it correctly on a wide range of factual questions, and the absence of a return schema is compensated by the explicit 'structured answer with citations' statement.

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 the required question parameter fully documented and aliases listed. The description adds no new per-parameter meaning beyond saying the tool fills arguments itself, but because the schema handles semantic load, the baseline of 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 names a specific verb-resource pair: ask_pipeworx routes a natural-language question to the right one of 5,798 tools across verified sources and returns a structured answer with citations. It clearly distinguishes itself from siblings by explicitly routing rather than doing a single narrow lookup, and differentiates against 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?

Usage direction is unusually explicit: it says 'PREFER OVER WEB SEARCH,' lists concrete domains, gives verb triggers, provides examples, and says 'START HERE for most questions.' It also names two alternatives and the exact conditions under which each should be chosen, making the decision procedure clear.

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