odoo_recent_changes

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

With no annotations provided, the description carries the transparency burden. It adds useful behavioral context by mentioning reliance on write_date/write_uid and visibility of interface changes by others. However, it does not disclose whether the operation is read-only, what kind of data is returned (e.g., changed records vs. a change log), or any limitations.

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 concise, consisting of two short sentences. It is front-loaded with the core purpose and adds a specific detail (seeing interface changes). No unnecessary filler, though the second sentence could be more informative if it described parameters or usage.

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?

The tool has 4 parameters, no annotations, and relies entirely on the description for context. The description gives a general idea but omits crucial usage details: the required 'model' parameter, the meaning of 'jours', the domain filter, and the output type (though an output schema exists). It fails to tell the user how to effectively invoke the tool.

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 schema has 0% description coverage for all 4 parameters, and the description does not mention any parameters. Parameter names like 'model', 'domain', 'jours', and 'limit' are somewhat self-explanatory in Odoo context, but the description fails to clarify their roles or required combinations, leaving significant ambiguity.

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 indicates the tool's purpose: showing what changed recently in Odoo based on the native audit fields (write_date, write_uid). It differentiates from sibling tools by focusing specifically on audit-based recent changes rather than general search/read, though it lacks an explicit verb like 'list' or 'return'.

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 implies a use case (tracking recent modifications, including interface changes by other users) but does not explicitly state when to use this tool over alternatives like odoo_read or odoo_search, nor does it mention any prerequisites or exclusions.

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