odoo_search_read

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

Annotations already indicate readOnly, openWorld, and non-destructive behavior. The description adds useful constraints: the model must be 'allowed' and the limit is bounded to a configured maximum. These go beyond the annotation defaults, providing context about system-imposed boundaries.

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 concise sentences: the first states the purpose, the second explains parameter semantics. No wasted words, all information is relevant and efficiently front-loaded.

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 output schema exists, return values are documented externally. The description covers purpose, parameter meanings, and key constraints (allowed model, bounded limit). It lacks details on optionality (e.g., domain default) and error behavior, but for a read operation with good annotations, this is reasonably complete.

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?

With 0% schema description coverage, the description compensates by explaining the meaning of 'domain' (Odoo search domain list), 'fields' (limits columns), and 'limit'/'offset' (pagination). The 'model' parameter is implied as the target of the read. This covers most parameters meaningfully, though 'model' lacks explicit detail.

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 reads records from an Odoo model, using the specific verb 'read' and naming the resource. It distinguishes itself from siblings: 'odoo_list_modules' lists modules, 'odoo_create_record' creates records, while this tool reads existing records.

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 clear context by explaining the parameters and noting the 'allowed' model restriction and bounded limit. It does not explicitly state when to use this tool over alternatives, but the read-only purpose is clear and it lacks exclusion criteria. A 4 is appropriate for clear context without explicit alternatives.

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