List Odoo models

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

Annotations already declare readOnlyHint and openWorldHint, so safety of the call is known. The description adds non-obvious context: models blocked by the safety policy are never listed, which explains why a model the agent expects may be absent. Pagination/limit behavior is left to 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?

Two short sentences, zero waste. The core purpose is front-loaded and the scope caveat follows immediately.

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?

With annotations covering read-only semantics and an output schema present, the description only needs to establish scope and any surprising behavior — which it does via the access scope and safety-policy exclusion. Only minor gap is that limit/pagination behavior is not mentioned.

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%, so each parameter is already fully documented, including that the query filters on technical name or label. The description only restates that filtering is by name, adding nothing beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource: 'List the Odoo models this server can access.' The scoping phrase 'this server can access' plus the safety-policy note makes the domain clear. It does not explicitly contrast with siblings like describe_model, but the resource (models vs records) already separates it.

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?

Usage is only implied ('optionally filtered by name'). There is no statement of when to prefer this over describe_model or search_records, and no prerequisites or exclusions beyond the safety-policy note.

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