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, so the bar for additional context is lower. The description adds real value by revealing that the tool fills arguments, routes to one of 5,798 tools across verified sources, and returns stable pipeworx:// citation URIs. No contradiction with annotations; it just doesn't discuss rate limits or failure modes, which is acceptable here.

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 useful guidance, but it is severely bloated: the same 'Use whenever... Examples...' block is repeated multiple times with no added information. This makes it much longer than necessary and undermines the structure, even though the opening paragraph is strong.

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?

Despite the redundancy, the description is functionally complete: it explains the input style, the covered domains, the routing behavior, and the output format with citation URIs. There is no output schema, so the description appropriately carries the return-value explanation. The only missing context is explicit routing among sibling ask_pipeworx variants, which is a minor gap here.

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%: the primary 'question' parameter and all five aliases are documented in the schema, so the baseline is 3. The description goes beyond the schema by giving trigger phrases and examples that clarify what kinds of natural-language inputs are appropriate, making the parameter semantics noticeably clearer.

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 states that the tool routes factual questions to one of 5,798 sub-tools and returns a structured answer with citation URIs, so the core action and resource are concrete. It distinguishes itself from web search through 'PREFER OVER WEB SEARCH', but it does not explicitly differentiate itself from sibling variants like 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 gives explicit when-to-use guidance with trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') and concrete example queries. It also names web search as the alternative to prefer this over, but it does not provide when-not-to-use guidance or compare against the other pipeworx sibling tools.

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