odoo_execute_kw

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

With no annotations, the description carries full behavioral burden and partially meets it by disclosing a firewall/policy layer and that responses can include 'human approval status' — meaningful for a tool that may mutate data. However it never states which methods are permitted or denied, what happens on rejection, permission requirements, or reversibility of create/unlink.

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?

Front-loaded one-line summary followed by clean Args/Returns sections. Every line carries information and there is no filler, though the Args examples are slightly repetitive in form.

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 not be explained, and parameters are well covered. What remains thin is the behavioral envelope — allowed/blocked methods, approval triggers, and error behavior — which for a generic executor exposed to destructive verbs like 'unlink' leaves the agent guessing.

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%, so the description must compensate, and it does: all four parameters are documented with concrete examples (model names like 'sale.order', methods like 'search_read'/'unlink', positional search domains/IDs, and kwargs like {'fields': [...], 'limit': 10}). This adds real invocation guidance beyond the bare schema.

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 specific verb+resource: executing an Odoo ORM method (execute_kw) through a firewall layer. It is immediately clear this is a generic ORM gateway rather than a fixed operation. No sibling tools exist to differentiate against, but the purpose itself is unambiguous.

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?

There is no explicit guidance on when to use this tool versus other approaches, nor which methods are safe or which trigger human approval. 'Safely execute ... via deterministic firewall rules' hints at guardrails but never states when the tool applies or what conditions block it.

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