odoo_search_read

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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds a genuine behavioral detail beyond those annotations: the operation runs with the permissions of the configured Odoo API user. There is no contradiction between the description and the annotations.

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 one tight sentence with no filler. It front-loads the core behavior and model scope, making it instantly scannable while still covering the most important distinguishing information.

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?

For a generic read tool with six parameters and no output schema, the description omits filtering semantics, field selection, pagination, ordering, and usage boundaries with siblings. An agent would need substantial external knowledge of Odoo to use this tool confidently beyond a trivial model-only call.

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%, with model and domain described in the schema but limit, order, fields, and offset left undocumented. The tool description itself only adds meaning for the model parameter ('any Odoo model') and does not compensate for the low coverage of the remaining five parameters.

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 states a specific action ('search and read records') and a clear resource ('any Odoo model'), which immediately distinguishes it from mutating siblings like odoo_create, odoo_write, and odoo_unlink. It also communicates the tool's general applicability across models rather than restricting it to a single model.

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?

There is no guidance about when to choose this tool over alternatives such as odoo_fields_get, nor any explicit statement that this is the read path while create/write/unlink are for mutations. The intended usage must be inferred from the tool name and sibling list rather than from the description.

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