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

Annotations already mark readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description goes further by detailing the exact success return shape, the explicit refusal shape, the refusal reason enums, and the behavioral guarantee that it does not invent facts. It also discloses the cost tradeoff (one extra LLM call). It does not mention rate limits or latency, but the disclosure is strong.

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 dense but front-loaded with the core value proposition, then the return shapes, then usage guidance, then cost tradeoff. It earns its length, though it could be slightly tightened without losing important behavioral detail.

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 single-required-parameter read-only tool with 100% schema coverage and no output schema, the description fully covers what the tool does, what it returns, when to use it, when not to use it, how refusal works, and the cost implication. Nothing essential is missing for an agent to invoke it correctly.

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 description coverage is 100%, so the schema already documents all aliases and the natural-language question parameter. The description repeats 'question' indirectly but adds no new parameter-level meaning beyond the schema, so baseline 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 this as a hallucination-resistant, grounded answer mode for high-stakes reads, with a specific verb (ask) and resource (Pipeworx). It distinguishes itself from ask_pipeworx by explaining it extracts answers only from tool results and returns evidence/refusals.

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?

Explicitly states when to use this tool: whenever an answer will be quoted, cited, or acted on, and provides concrete examples (financial verdicts, legal claims, medical lookups, public statements). It also names the alternative (ask_pipeworx) and directs casual lookups there, citing the extra LLM call cost.

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