execute_method

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

Annotations already indicate destructiveHint=true and idempotentHint=false, so the description's statement 'execute a custom method' implies arbitrary behavior but adds no new context about side effects, authentication needs, or safety precautions. It merely restates the obvious given the annotation flags.

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 sentence, which is concise but lacks structured details. It is appropriately short but does not provide substantial guidance. Every word earns its place, but the sentence is too brief to be highly informative.

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?

Given the tool's complexity (openWorldHint, 5 parameters, many sibling tools) and the rich output schema, the description is severely incomplete. It fails to clarify usage context, parameter roles, or how this tool relates to siblings. The output schema exists but no cross-reference is made.

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% – no parameter descriptions exist in the schema. The description 'Execute a custom method on an Odoo model' does not explain any of the five parameters (model, method, args, kwargs, instance). Parameter names are somewhat self-explanatory, but the tool would benefit from explaining how to use args/kwargs, especially given the open-world nature.

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 'Execute a custom method on an Odoo model' clearly states the action (execute) and resource (custom method on Odoo model). However, it does not differentiate from sibling tools like 'execute_approved_write' or 'preview_write', which are more specific. The word 'custom' hints at flexibility but could be more explicit.

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 no guidance on when to use this tool versus alternatives like 'execute_approved_write' or 'search_records'. It lacks explicit 'when to use' or 'when not to use' information, leaving the agent to infer from the tool name alone.

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