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

Annotations only declare destructiveHint=true; the description adds valuable context beyond that by stressing 'This MODIFIES live billing data' and including the underlying REST call and return shape. It stops short of disclosing reversibility (whether a skipped charge can be un-skipped) or auth/permission requirements.

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 dense sentences that are front-loaded with the effect and the mutation warning, followed by the API detail. No filler; every sentence carries information.

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 two-parameter mutation tool with no output schema, the description covers what it does, that it alters live billing data, and the return shape ('Returns { charge }'). Minor gaps remain on reversibility and failure/permission behavior.

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 coverage is 100%, so both parameters are already documented, and the schema itself notes 'some stores require this' for purchase_item_ids. The description largely restates that and adds only the JSON body shape, so the 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?

States a specific verb and resource ('SKIPS a scheduled charge — prevents it from processing on its scheduled date') and clearly distinguishes itself from read-oriented siblings like recharge_get_charge and recharge_list_charges.

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?

Explains the scenario for use (preventing a scheduled charge from processing) and the condition under which purchase_item_ids is required ('Some stores require the specific line items'). It does not explicitly name alternative tools or state when not to use it, so it falls short of a 5.

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