call_method

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

Annotations already set destructiveHint=true, so description doesn't need to repeat that. Description adds that the tool accepts model, method, ids, and params, but does not explain behavior like side effects on different record IDs or error handling, which would add value beyond 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?

Extremely concise: two sentences plus a clear argument list. No unnecessary words, front-loaded with purpose and usage guidance. Every sentence earns its place.

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 absence of output schema, description should indicate return value (e.g., the method's result). It also does not clarify behavior when 'ids' is null (operates on all records? or none?). These gaps reduce completeness despite good parameter explanations.

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%, but description fully explains all four parameters: model, method, ids (optional list of IDs), and params (optional dict of kwargs). This provides meaning beyond the schema's type/title, compensating for lack of schema descriptions.

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?

Description clearly states 'Call any public method on an Odoo model', using a specific verb and resource. It differentiates from sibling tools like get_model_doc (discovery) and create_record (creation).

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 to 'Use get_model_doc first to discover the correct parameter names and types', setting a clear precondition and suggesting an alternative for discovery. Lacks explicit when-not scenarios but provides enough context.

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