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

Annotations already declare destructiveHint=true, idempotentHint=true and non-read-only, so the safety profile is covered. The description adds genuinely new behavior: the payment date is forced to today and payment reminders are stopped as a side effect — context an agent cannot derive from annotations alone.

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 short sentences with zero waste; the core action is front-loaded and the side effect follows. Nothing is padded.

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 one-parameter mutation tool with annotations covering idempotency and destructiveness, the description supplies the two non-obvious facts (date defaults to today, reminders stop). Only minor gaps remain, such as authorization requirements or behavior when the invoice is already marked paid.

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% and the single invoiceId parameter has no textual explanation, but its meaning is self-evident from the name and the format/pattern constraints in the schema. The description adds only an implicit reference to 'an invoice' rather than parameter-level semantics.

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 ('Record that the client has paid an invoice') with clear scope, and the sibling tools (create_invoice, send_invoice, list_invoices) are distinct enough that the action is unambiguous. It does not explicitly name a sibling to differentiate against, keeping it just short of a 5.

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?

No guidance on when to use this vs alternatives such as add_transaction, nor any prerequisites or exclusions. The mention of '(dated today)' implies a usage constraint but is stated as a side effect, not as usage guidance.

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