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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are scoped to the signed-in company, names use Odoo's display form, journals the user cannot use are excluded, and it requires a Cotlet API key with app access. That auth requirement and filtering rule are not derivable from annotations.

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 sentences, each earning its place and front-loaded: purpose, return contents, downstream usage, filtering rule, then the auth prerequisite. No repetition of the title or schema, no padding.

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 zero-parameter read tool with no output schema, the description covers everything an agent needs: what it returns, the name format, which journals are excluded, the auth requirement, and how to consume the result. Nothing essential to correct invocation 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?

Zero parameters, so the baseline is 4 and the schema (empty, additionalProperties false) carries no parameter burden. The description still adds return-value semantics — the name format to pass onward to register_payment — which is valuable since no output schema exists. It is not a 5 only because there is little parameter surface to illuminate.

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 (List) and resource (bank and cash journals) with scope clarified ('journals you can register payments on'). It distinguishes itself from siblings by tying directly to register_payment, so an agent can tell it apart from odoo_register_payment or odoo_list_invoices without opening either 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?

Explicitly tells the agent what to do with the result ('Pass the name to register_payment as journal'), naming the sibling and the exact field. This is a clear when-to-use signal with a defined downstream action, not just implied context.

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