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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is partly met structurally. The description adds real value beyond them by guaranteeing no charges, no retries, and no provider execution, plus that verification is free — exactly the side-effect concerns an agent would have about a tool touching payments.

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?

Two tight sentences, purpose first and the safety guarantee second. No filler, nothing restated from the title.

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 tool with a three-way branching input contract, undefined parameter meanings, and no output schema, the description leaves too much unanswered — notably what a verification response looks like and how statusCode/content/sources change behavior. Adequate only for the safety story.

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 0% across 5 parameters (including nested objects), so the description must carry the burden. It only gestures at 'receipt' and 'failure'; statusCode, content, and sources are never mentioned, and the anyOf requirement that exactly one of receipt/failure/statusCode be supplied is left undocumented.

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?

States two concrete modes with specific verbs and objects: verifying a PHION receipt and converting a failed status into a next repair action. The closing clause ('never charges, retries, or executes a provider') separates it from the execute sibling, though no sibling is named explicitly.

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?

Usage conditions are implied by the two described inputs (have a receipt → verify; have a failed status → get next action), but there is no explicit when-not guidance and no naming of authorize_and_execute_selected_task or find_or_quote_task as the alternatives for the cases this tool refuses to handle.

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