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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior, so the description adds useful operational context: it routes to the right tool, fills arguments, and returns structured answers with pipeworx:// citations. It also discloses a 'too short answer' failure mode and advises rephrasing. No contradiction with annotations, though it doesn't discuss failures, rate limits, or edge-case 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 key routing directive ('PREFER OVER WEB SEARCH') and structured with examples, a routing decision list, and a closing practicality note. It earns its length given the many sibling tools, though the routing list is somewhat repetitive and could be tightened.

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 still explains the return format: 'structured answer with stable pipeworx:// citation URIs.' It covers main use cases, examples, alternatives, and one failure/rephrase guidance. It is nearly complete, but it does not explicitly distinguish ask_pipeworx_beta or explain what happens when no source matches the question.

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%: the only required parameter, question, is described as a natural-language request, and the five other parameters are explicitly documented as aliases. The description adds minimal parameter-level guidance, but the schema already carries the full semantic burden, so baseline 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 opens with 'PREFER OVER WEB SEARCH' and clearly states what the tool does: routes the question across 5,798 tools from 1,517 verified sources and returns structured answers with stable pipeworx:// citation URIs. It lists concrete domains and examples, so an agent can easily distinguish this from sibling search and research 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?

Gives explicit selection criteria: use it for factual questions involving 'what is', 'look up', 'find', 'get the latest', 'how much', or 'current', and says 'START HERE for most questions.' It also names alternatives such as ask_pipeworx_grounded, search, deep_research, compare_entities, resolve_entity, and web-search with the conditions under which they should be preferred.

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