odoo_search_read

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

With no annotations provided, the description carries the full burden. It mentions that the tool does not expose credentials or sensitive fields and that records are bounded, which provides some behavioral context. However, it lacks details on idempotency, side effects, or authentication requirements.

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, making it concise, but it front-loads the purpose adequately. However, it lacks structure and could benefit from brief parameter highlights or usage context without becoming verbose.

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 tool has 6 parameters (3 required), an output schema, and no description for any parameter, the single-sentence description is insufficient. It does not address return values, pagination, or parameter interplay, leaving gaps for an agent to correctly invoke the tool.

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 0%, and the tool description does not explain the meaning or usage of any parameters (model, domain, fields, etc.). This fails to add value beyond the raw schema, which is critical for a tool with 6 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 clearly states the tool reads bounded Odoo records and emphasizes security by not exposing credentials or sensitive fields. It distinguishes from sibling tools like apply_odoo_mutation and odoo_change_history, which are mutation or info tools.

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 implies usage for reading bounded records, but provides no explicit guidance on when to use this tool versus alternatives like odoo_fields_get or when not to use it. The context is implied but not specified.

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