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

Annotations already declare destructiveHint and non-idempotency, but the description adds the actual consequence — the saved payment method is charged and an order is created — plus a repeat-call warning and the confirm requirement. That is exactly the supplemental context annotations cannot convey.

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?

Four short, front-loaded clauses: nature of the operation, outcome, guardrails, and the underlying endpoint. No filler, and the highest-risk information (money movement) comes first.

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 with no output schema, the description covers the trigger conditions, the side effects, the idempotency risk, and the success outcome. Nothing an agent needs before calling is missing.

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% and already documents both fields, so the baseline applies; however the description adds value by reinforcing that confirm must be true and by pointing to smartrr_list_bills as the source of bill_id. Minor added meaning beyond the schema.

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?

Opens with a specific verb and resource ('retry a billing attempt') and immediately flags the write/charge nature. It is clearly distinguishable from read-only siblings like smartrr_list_bills and smartrr_get_bill_history.

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?

Gives an explicit prerequisite ('Check the bill with smartrr_list_bills first'), an exclusion ('do not retry a succeeded bill'), and the confirm=true gate. This is textbook when-to-use/when-not-to-use guidance with the alternative named.

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