execute_action

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

Discloses execution mechanism (view buttons call method directly, server actions use ir.actions.server.run) and return types (action result, {success:true}, or {error}). With no annotations, could better state potential side effects (destructive hints) but still adds meaningful behavioral context.

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 sentences plus a technical note, all front-loaded. Every sentence adds value, no redundancy. Efficient and clear.

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?

Covers purpose, parameter semantics for action, usage hint, and return format. With no annotations or output schema, could specify permissions or error handling more, but overall sufficient for an AI agent to use the tool correctly.

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 coverage is 0%, so description carries burden. Explains action parameter in detail (button name/label, examples, view vs server), but provides no extra meaning for model or record_id beyond their names. Adequate but not comprehensive.

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 'Execute a button or server action on a record' with clear verb+resource. Distinguishes from siblings by referencing find_skill/list_workflows for canonical recipes and get_model_actions for action names, establishing when this tool is appropriate.

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 advises checking canonical recipes before multi-step work. References sibling get_model_actions for action parameter guidance. Lacks explicit 'when not to use' but provides clear context.

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