Execute Method

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

Goes well beyond the destructiveHint=true annotation by naming concrete dangerous methods (action_confirm, action_post, button_validate, toggle_active), disclosing that state changes can be irreversible, and warning explicitly that the server does NOT guard these calls. That is exactly the context an agent needs beyond structured fields.

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?

Purpose is front-loaded in the first sentence, followed immediately by the safety warning. No filler; every sentence carries weight for a dangerous tool.

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?

An output schema exists, so return values need no explanation, and destructiveHint covers the safety profile. Combined with the explicit warning about unguarded business methods, an agent has everything needed to decide whether and how to call this.

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 model, method, args, and kwargs are already documented in the schema. The description adds no format, ordering, or shape guidance for args/kwargs, 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 (execute) and resource (method on an Odoo model) and self-classifies as a 'general-purpose escape hatch,' which cleanly distinguishes it from the CRUD-specific siblings like create_record, update_record, and delete_record.

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?

Provides a clear precondition: 'Before calling any method that changes state, make sure the user explicitly asked for it.' This gives real when-to-use guidance, but it never routes the agent to the dedicated siblings (e.g. use update_record for standard writes) or states when this escape hatch is appropriate for reads.

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