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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the exact success and refusal return shapes, the refusal reasons, the evidence-only extraction constraint, and the extra LLM call cost. It does not contradict any annotation, and it makes the tool's safety and failure behavior explicit.

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 well structured: mode, mechanism, returns/refusals, use cases, and trade-off all appear in logical order with no filler. Every sentence carries operational information an agent needs to invoke and interpret the tool.

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?

With no output schema, the description fully covers expected return fields and explicit refusal variants, and it also explains when to prefer this over ask_pipeworx. Given the tool's complexity, nothing essential is missing for correct invocation and response handling.

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 baseline is 3 and the schema fully documents the required 'question' parameter and its aliases. The description adds no parameter-specific detail beyond mentioning that arguments are filled, so it neither improves nor harms parameter clarity.

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 names a specific operation: a hallucination-resistant, evidence-only answer mode that routes a question through the same pipeline as ask_pipeworx and extracts the answer strictly from tool results. It explicitly contrasts with the sibling ask_pipeworx by emphasizing grounded extraction and refusal behavior, so an agent can tell them apart.

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?

It gives explicit when-to-use guidance ('whenever an answer will be quoted, cited, or acted on') and names the alternative with a cost-based exclusion ('Costs one extra LLM call vs ask_pipeworx — prefer ask_pipeworx for casual lookups'). This is strong routing guidance, not just implied context.

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