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

Annotations only declare it is a non-destructive, open-world write. The description adds the state transitions (In payment, then Paid after reconciliation), the failure conditions, the permission requirement (invoicing users), the API-key requirement, and the confirmation-before-each-call policy. That is rich context the annotations do not carry.

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?

Front-loads what the tool does before the caveats, and most sentences carry information. Slightly diluted by two sentences covering the confirmation policy and a trailing boilerplate note about the API key.

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, yet the description explains the resulting invoice states, failure modes, permissions, and confirmation behavior. Everything an agent needs to invoke this mutation correctly is present.

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 100%, so the schema already documents all five parameters including defaults and cross-references. The description adds only minor framing ('Fills the Pay window') and no new parameter-level meaning, so the baseline 3 applies.

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 ('Register a payment on a posted invoice') and scopes it to the Pay window workflow. Reading it, an agent can distinguish this from odoo_post_invoice, odoo_send_invoice, and odoo_create_draft_invoice without opening any 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?

Gives clear preconditions: the invoice must be posted, and the call fails if it is a draft or already Paid. This tells the agent when the tool is valid but stops short of naming sibling alternatives (e.g. post or send the invoice first) explicitly.

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