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

Annotations already establish read-only, open-world, and idempotent behavior. The description adds non-obvious behavioral context: it dispatches to thousands of internal tools, auto-fills arguments, and returns stable pipeworx:// citation URIs. This goes beyond the annotations and helps an agent predict how the output will be structured. No contradiction with annotations.

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 front-loaded with the key preference and behavior, and the examples are useful. However, it is verbose and somewhat redundant: 'PREFER OVER WEB SEARCH', 'Use whenever...', and 'START HERE' repeat similar guidance. The incomplete 'For .' ending also weakens the structure.

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 broad router tool with no output schema, it covers the core facts: scope, routing behavior, citation output, and examples. But it lacks explicit guidance about when to prefer sibling tools such as ask_pipeworx_grounded, ask_pipeworx_beta, or deep_research, and the broken closing sentence leaves the selection story incomplete.

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?

The input schema already documents all six aliases and the natural-language 'question' property with 100% coverage. The description's examples reinforce what kinds of questions are acceptable, but they do not add substantial meaning about individual parameter semantics beyond what the schema already provides.

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 clearly defines the tool as a question router: it routes to one of 5,798 tools across 1,517 sources, fills arguments, and returns a citation-backed answer. This is much more specific than the title. However, it does not explicitly distinguish the tool from sibling variants such as ask_pipeworx_beta or ask_pipeworx_grounded.

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' and gives strong trigger phrases like 'what is', 'look up', 'find', and 'get the latest', plus concrete examples. It also says 'START HERE for most questions,' but it never states when not to use this tool or when to choose a sibling; the final 'For .' fragment appears to be a truncated alternative comparison.

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