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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior, and the description adds real behavioral context: it routes among 5,743 tools, fills arguments, and returns pipeworx:// citation URIs. There is no contradiction with annotations, though failure cases and limits are not mentioned.

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 and organized, but it has redundancy: the phrase even if web search could also answer it appears twice, and the final START HERE sentence repeats the opening preference. The domain list and examples are useful, so it is not a low score.

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-required-parameter router with no output schema, the description is nearly complete: it covers scope, when to use, example queries, routing behavior, and output citations. It omits how it relates to ask_pipeworx_beta and ask_pipeworx_grounded and what happens when no authoritative answer exists, which is a minor gap.

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 schema has 100% parameter coverage and clearly documents the natural-language question parameter plus aliases. The description's examples illustrate query semantics, but they largely mirror the schema examples and add little new parameter-level meaning, so the baseline of 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 clearly identifies a specific verb and resource: it routes a factual question to the right specialized tool and returns a cited structured answer. It draws a strong contrast with web search, but it does not explicitly differentiate ask_pipeworx from sibling variants ask_pipeworx_beta and 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?

Usage guidance is explicit and actionable: it opens with PREFER OVER WEB SEARCH, says to use whenever the user asks factual questions, and provides concrete examples. It stops short of a 5 because it does not name when-not-to-use cases or point to sibling alternatives like deep_research or validate_claim.

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