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

Annotations already mark readOnly/openWorld/idempotent, and the description adds behavioral detail: it routes to 5,798 tools, fills in source-specific arguments itself, and returns structured answers with stable pipeworx:// citation URIs. It also frames the tool as a default before other research tools. No contradictions.

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 most important directive ('PREFER OVER WEB SEARCH') and each sentence adds a distinct piece: scope, mechanism, trigger phrases, examples, and alternatives. It is long but earned, since this is a high-traffic default tool that needs routing clarity.

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 router with no output schema and a broad scope, the description supplies enough: when to invoke, what it returns (structured answers with citations), how it operates, and when not to use it. The parameter and alias details are already in the schema, so nothing critical is missing.

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 all params are aliases for the natural-language question; the description adds the key semantic fact that the tool 'fills arguments' itself, so the agent only needs to supply a question, not source-specific parameters. The many examples clarify acceptable phrasing. It therefore goes beyond the schema's alias listing.

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?

Clearly describes a factual-question routing tool: take a natural-language question, route it to one of many source-specific tools, and return a cited structured answer. It lists the resource domain (authoritative structured data with citations) and explicitly contrasts with siblings like search_within, deep_research, and validate_claim, so an agent can distinguish its role.

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?

Includes strong when-to-use triggers ('what is', 'look up', 'get the latest', 'current') and says to prefer it over web search. It names explicit alternatives: search_within/ask_pipeworx_grounded for specific corpora, deep_research for synthesis, validate_claim for verification. However, it does not mention the sibling ask_pipeworx_beta, so an agent choosing between the stable and beta variants gets no guidance.

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