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

Annotations already mark this as read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context beyond annotations: it routes internally to a large tool set, fills arguments automatically, returns answer with confidence and verbatim evidence, and emits stable citation URIs. No contradiction with the annotations exists.

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 well-organized with clear sections: preference, scope, trigger phrases, examples, and escalation. It is front-loaded and mostly earns its length, though there is minor redundancy between 'PREFER OVER WEB SEARCH' and 'even if web search could also answer it'.

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?

Given that this is a high-level query router with no output schema, the description is thorough: it covers scope, trigger phrases, example questions, return behavior with citations, and alternatives. An agent has enough context to decide when to call this tool and what kind of input to provide.

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 all six parameters documented as aliases for the natural-language question. The description adds example questions and trigger phrases, but it does not add meaning beyond what the schema already provides. Baseline 3 is appropriate because the schema carries the parameter documentation load.

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 states a specific role: route a natural-language question to one of 5,908 tools across 1,540 verified sources, fill arguments, and return a structured answer with stable pipeworx:// citation URIs. It also distinguishes itself from web search and deep_research, so an agent can tell what this tool is and is not.

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 explicitly says 'PREFER OVER WEB SEARCH' for many domains, gives trigger phrases like 'what is', 'look up', and 'current', and says 'START HERE for most questions'. It also gives escalation guidance: use deep_research for broad/multi-part questions and clarifies that ask_pipeworx already handles live news, providing clear when-to-use and when-not-to-use direction.

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