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

Annotations already declare read-only, idempotent, open-world behavior. The description adds useful behavioral context: it routes to relevant tools, fills arguments, and returns stable pipeworx:// citation URIs. Nothing contradicts the annotations, and the added detail goes beyond the annotation hints.

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 first several sentences are concise and front-loaded, but the description degenerates into repeated blocks of 'START HERE for most questions — even if web search could also answer it. Examples: ...' that appear multiple times and seem to loop indefinitely. This is severe bloat and could mislead or stall an agent's parsing of the description.

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?

The description covers the tool's function, input style, usage triggers, and the citation-bearing output, which is enough to invoke it correctly. However, there is no output schema and no detail about the structured answer's shape, nor any mention of failure/limitation behavior; the sibling variants are also unaddressed. The repetitive tail adds no completeness.

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%, so the parameter is already well documented. The description supplements this by showing examples of valid natural-language questions and the kinds of phrasing that work. It does not explain aliases, but the schema already does; the examples add practical selection guidance.

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 core purpose is explicit: this tool routes a natural-language question to one of 5,798 tools across verified sources and returns a structured answer with citation URIs. The covered domains and authoritative-data positioning are clear. However, it does not distinguish ask_pipeworx from its sibling variants (ask_pipeworx_beta, ask_pipeworx_grounded), so an agent cannot tell which variant to select.

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 gives strong when-to-use guidance: prefer over web search, use for factual/current/historical questions, and even when web search could answer it. It provides trigger phrases and concrete examples. It lacks any when-not-to-use conditions or guidance about choosing among closely related sibling tools.

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