odoo_register_payment

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

With no annotations, the description must fully disclose behavioral traits. It only states 'registers a payment' without mentioning side effects (e.g., invoice state change, reconciliation), authorization requirements, or constraints. This is insufficient for a financial transaction tool.

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 description is a single, concise sentence. It is not overly verbose, but it could be more informative without sacrificing conciseness. It is acceptable in length but lacks substance.

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 financial operation with an output schema and multiple parameters, the description is too minimal. It does not explain the return value, potential errors, invoice state requirements, or any post-payment effects. The high number of sibling tools also necessitates more context for selection.

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?

The description adds no information about parameters beyond what the schema already provides. Schema description coverage is 0% and the tool has 5 parameters, yet the description does not explain their purpose or usage. The schema itself has good descriptions, so the description offers no added value.

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?

The description clearly states the tool registers a payment for a customer or vendor invoice. However, it does not differentiate from the similar sibling tool 'odoo_register_invoice_payment', which likely has overlapping functionality.

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 is provided on when to use this tool versus alternatives like 'odoo_register_invoice_payment' or other payment-related tools. The description lacks any context about prerequisites or typical use cases.

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