odoo_list_models

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

No annotations are provided, so the burden falls on the description. It does not disclose that this is a read-only operation, whether authentication is required, if results are paginated, or what the limit parameter does behaviorally beyond the schema.

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 a single sentence, which is concise but too brief. While it has no fluff, it misses opportunities to add useful context within a compact structure.

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 no output schema and no annotations, the description lacks completeness. It does not describe the return format (e.g., list of model names), pagination behavior, or any prerequisites. Users would need to infer tool behavior from the name alone.

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 only 33% (only pattern has a description). The tool description adds minimal value: 'Optionally filter by name pattern' merely restates the pattern parameter. It does not explain 'connection' or 'limit', leaving parameters poorly documented.

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 it lists Odoo models (ir.model) with optional filtering by name. This uniquely identifies the tool's purpose among many sibling odoo_* tools like odoo_search, odoo_fields_get, etc.

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 only notes optional filtering but provides no guidance on when to use this tool versus alternatives like odoo_search or odoo_read. No when-to-use or when-not-to-use context is given.

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