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

The annotations already include readOnlyHint: true, which covers safety. The description adds no behavioral detail beyond the literal purpose—it does not mention return format, whether it lists all models or only installed ones, or any limits/performance characteristics. It adds no value beyond the annotation and the tool's obvious read-only nature.

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?

A single, focused sentence with no wasted words. The core purpose is front-loaded and the description is appropriately sized for a simple listing tool. It is concise without being under-specified to the point of confusion.

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 is simple: two optional parameters, an output schema, and a read-only annotation. The description states the basic purpose, and the output schema covers return values. However, it lacks any guidance on when to use this tool relative to siblings or what the filter can do, making it slightly incomplete for an agent operating in a broader Odoo toolset.

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 100%, with both 'limit' and 'filter' having explicit descriptions in the schema. The description adds no further clarification or example of how to use the parameters, so the baseline of 3 applies without additional contribution from the description.

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 'Descubre modelos disponibles en Odoo' uses a clear verb (descubre/discover) and specific resource (modelos disponibles en Odoo). It conveys the tool's purpose effectively. However, it does not explicitly differentiate it from sibling tools like odoo_fields_get or odoo_search_read, relying instead on the tool name and contextual inference.

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. There are no exclusions, no mention of using it as a precursor to other Odoo operations, and no reference to the filter capabilities that might make it useful for targeted discovery. Usage context is entirely absent.

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