Execute custom Odoo method

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

Annotations declare destructiveHint=true and readOnlyHint=false, which properly signal the tool can modify data. The description adds one behavioral fact: 'Requires confirmation' – implying the agent must set the 'confirmed' parameter to true explicitly. This is useful and goes beyond the annotation. However, it doesn't describe what happens if confirmed is false (does it error? return a confirmation request?), what side effects the method may have, or whether the method is executed in a transaction. With annotations covering the destructive nature, a 3 is fair: adds some value but leaves important behavior opaque.

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 brief—two short sentences. It's front-loaded with the core purpose and includes a critical behavioral hint (confirmation). No wasted words. However, given the complexity of a generic method executor, this brevity borders on under-specification, but it's still concise and to the point.

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?

The tool has 5 parameters, an output schema, and destructive annotations. The description is far too thin to fully equip an agent. It doesn't explain the confirmation flow (how to interpret a false 'confirmed' response), what kind of output to expect, or any restrictions on method names (e.g., should only call methods that are safe?). The output schema exists but the description doesn't guide interpretation. Compared to sibling tools like aidoo_create or aidoo_write which have richer descriptions, this one leaves too much to inference.

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 0% – the parameter names (model, method, args, kwargs, confirmed) are present in the schema but have no descriptions. The tool description provides zero explanation of what each parameter means. For instance, 'confirmed' is a boolean that likely must be true to execute, but the description doesn't state that clearly beyond 'Requires confirmation.' The agent must infer that 'confirmed' gates execution. Similarly, 'args' and 'kwargs' are self-explanatory to an Odoo expert but not explicitly tied to the method call. The description fails to compensate for the 0% schema coverage.

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 states a clear verb and resource: 'Execute a custom method on an Odoo model.' This distinguishes it from generic CRUD tools like aidoo_create or aidoo_write, which handle standard methods, whereas this executes arbitrary custom methods. However, it doesn't specify what kind of custom methods (e.g., business logic, complex operations) or contrast with aidoo_workflow_run, which might also trigger custom logic. Overall, purpose is clear but slightly under-specified.

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?

The description provides almost no guidance on when to use this tool versus alternatives. It doesn't mention that aidoo_create/aidoo_write/aidoo_delete should be preferred for standard CRUD, nor does it warn against using it for read-only custom methods (which might be better via aidoo_query/aidoo_read). The 'Requires confirmation' hint is present but not expanded; there's no explanation of when confirmation is needed or how to approach it. No explicit exclusions or context for selection.

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