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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, and the description complements them rather than repeating them: the money movement is immediate, an order is created, the schedule is otherwise untouched, and reset_schedule rebuilds subsequent attempts from today. Remaining gaps are failure/retry behavior when the charge is declined and whether this is the same path as process_charge.

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 consequence and the WRITE marker are front-loaded, and each following sentence adds a distinct fact (immediacy, call guard, reset_schedule effect). The all-caps emphasis and the trailing 'PUT /subscription-create-charge-now' are mildly noisy but do not bury the key 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, no-output-schema mutation tool, the description covers trigger condition, immediate effect, side effect (order creation), and the schedule consequence. An agent has enough to decide to call it and to set reset_schedule correctly; return-value detail is not required here.

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 a 3 is the baseline; the description earns a bump by making reset_schedule's effect concrete ('later attempts are rebuilt from today') rather than the schema's vaguer 'rebuild the rest of the schedule'. subscription_id is left entirely to the schema, which is fine given its coverage.

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?

Specific verb and effect: immediately charges the customer's payment method for the next billing attempt and creates a Shopify order. It also states the negative scope ('does not wait for the scheduled date'), which separates it from scheduled-billing behavior. What keeps it from a 5 is that it never names the closest sibling (sealsubscriptions_process_charge) that an agent would otherwise confuse it with.

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?

'Only call it when the user clearly asked for an immediate charge' is an explicit and unusually strong gate on a destructive tool. It also explains how reset_schedule changes the outcome. There is no guidance on what to do instead when the user did not ask for an immediate charge (e.g., reschedule_billing_attempt, skip_billing_attempt).

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