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

Beyond the readOnly/idempotent/openWorld annotations, it discloses the routing behavior, automatic argument filling, structured answer format, and stable pipeworx:// citation URIs. This is substantive context about what happens when the tool is called.

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 dense but front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and organized around scope, behavior, triggers, and examples. The domain and example lists are long but earn their place; the trailing ellipsis is slightly untidy.

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 one-parameter tool with strong annotations, the description covers purpose, usage, behavior, and output format well. It is not fully complete because it never tells the agent how to choose among the sibling variants (e.g., ask_pipeworx_beta/grounded), relying instead on 'START HERE for most questions.'

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% and the schema already describes 'question' as a natural-language request with aliases, so the baseline is 3. The tool description adds examples and trigger phrases, but these are more about usage context than new parameter-level semantics, and it does not resolve the required-vs-alias ambiguity in the schema.

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 action ('routes the question to the right one of 5,798 tools...') and lists the covered domains, so an agent understands it is a factual data-query router. It does not explicitly distinguish itself from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded, so it falls short of full sibling differentiation.

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?

It gives clear when-to-use guidance: 'PREFER OVER WEB SEARCH' and 'Use whenever the user asks...' with trigger phrases and concrete examples. It does not state when not to use it or point to any specific alternative tool, so it lacks explicit exclusions.

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