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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds genuinely new context that a 'destructive' flag alone would not convey — namely that no money is charged or debited and that the call is inert without confirm. It stops short of describing success/failure outcome or reversibility (whether recharge can be re-enabled).

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?

Three short sentences, front-loaded with the action and its consequence, then the non-effect, then the precondition. Nothing is redundant.

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?

No output schema exists, and the description adequately covers what the tool does and does not do. It leaves the return value and error behavior unspecified, which is a small gap for a state-changing wallet operation.

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% for the single `confirm` boolean, so the description must carry the load — and it does, stating that nothing happens unless confirm=true, which implies the default and the gate. This is more than the schema provides.

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 a specific verb and resource ('Turns off wallet auto-recharge') plus the operational consequence ('so a saved card is not charged later'). No sibling tool touches auto-recharge, and the description makes the scope unambiguous without needing the schema.

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 the activation precondition ('Does nothing unless confirm=true'), which is the key usage decision for this tool. It does not name alternatives or when-not-to-use, but no sibling offers an equivalent capability, so the gap is minor.

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