MCP Odoo Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the state change and returns a confirmation message, but fails to detail critical aspects like required permissions, whether the action is reversible, error conditions, or side effects. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by brief sections for Args and Returns. Each sentence earns its place without redundancy, making it efficient and easy to parse. The structure is clear and minimalistic.

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 (a mutation with 1 parameter) and the presence of an output schema (which handles return values), the description is moderately complete. It covers the basic action and parameter semantics but lacks behavioral details like permissions or error handling. With no annotations and an output schema, it meets a minimum viable level but has clear gaps for safe and effective use.

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. It adds meaning by explaining that 'allocation_id' is the 'Allocation ID to approve', clarifying its role beyond the schema's basic type (integer). However, it doesn't provide format details or examples, and with only 1 parameter, the baseline is high. The description adequately covers the parameter's purpose but could be more detailed.

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 clearly states the verb ('approve') and resource ('leave allocation'), and specifies the state transition ('from draft/confirm to validate'). It distinguishes this from sibling tools like 'create_leave_allocation' or 'list_leave_allocations' by focusing on approval rather than creation or listing. However, it doesn't explicitly contrast with other approval-related tools if they existed, keeping it at 4 rather than 5.

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 minimal guidance on when to use this tool—it implies usage for approving leave allocations in specific states (draft/confirm). However, it lacks explicit context on prerequisites (e.g., permissions needed), alternatives (e.g., other tools for rejection or editing), or exclusions (e.g., when not to use it). No sibling tools are directly referenced for comparison, resulting in limited guidance.

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