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

The description discloses many non-obvious behaviors beyond the annotations: the exact success response shape, the explicit refusal reason enum, the constraint that extraction uses only the tool result, and the extra LLM call cost. These align with the readOnly, non-destructive annotations and add substantial transparency.

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 every sentence earns its place: behavior, routing mechanism, response format, refusal modes, usage context, and cost trade-off. It is front-loaded with the key differentiator and contains no filler.

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 specifies the return shape and refusal reasons, and it covers when to use the tool, alternatives, and cost. It relies on the schema for parameter details and on sibling definitions for routing context, which is reasonable but leaves a small dependency on ask_pipeworx's description.

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 input schema already documents the parameters. The description only says it 'fills arguments' and does not add parameter-specific meaning beyond that, so the baseline 3 applies.

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 states a specific capability: a hallucination-resistant answer mode for high-stakes reads, using the same routing as ask_pipeworx but extracting answers solely from tool results. It goes well beyond the title and clearly distinguishes the tool from its sibling by describing the refusal behavior and extra cost.

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 explicitly says when to use the tool: 'Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts,' with concrete examples like financial verdicts and legal claims. It also gives the exclusion rule: 'prefer ask_pipeworx for casual lookups,' naming the alternative directly.

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