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 states the tool creates a report and returns a confirmation with an ID, but lacks critical details: whether this is a mutation (implied by 'create'), what permissions are required, if it's idempotent, error conditions (e.g., invalid expense IDs), or side effects (e.g., report status changes). For a creation 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 well-structured and concise, with zero wasted text. It front-loads the core purpose in one sentence, followed by clear Arg/Return sections. Every sentence earns its place by directly contributing to understanding the tool's function and parameters, making it easy to scan and comprehend quickly.

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 creation operation with 2 parameters), lack of annotations, and presence of an output schema (which handles return values), the description is minimally adequate. It covers the basic purpose and parameters but misses behavioral context (e.g., mutation effects, error handling) and usage guidelines. The output schema likely details the confirmation structure, so the description doesn't need to elaborate on returns, but overall completeness is limited to the essentials.

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?

The description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'name' is the 'Report name/title' and 'expense_ids' is a 'List of expense IDs to include in the report,' clarifying their roles in report creation. However, it doesn't detail constraints (e.g., name length, valid ID sources) or provide examples, preventing a perfect score. With 2 parameters and no schema descriptions, this compensation is adequate but not comprehensive.

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 tool's purpose: 'Create an expense report from selected expenses.' It specifies the verb ('create') and resource ('expense report'), and distinguishes it from siblings like 'create_expense' (which creates individual expenses) or 'submit_expense_report' (which submits an existing report). However, it doesn't explicitly contrast with 'list_expense_reports' (which lists reports) or other report-related tools, keeping it from a perfect score.

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. It doesn't mention prerequisites (e.g., needing existing expenses via 'list_expenses'), exclusions (e.g., not for editing reports), or comparisons to siblings like 'submit_expense_report' (for submitting after creation). The agent must infer usage from context alone, which is insufficient for effective tool selection.

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