odoo_search_read

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

No annotations are present, so the description must fully explain behavior. It only states 'Search and read records in one call', omitting details like default limit/offset, pagination, error handling, or authentication requirements. This is insufficient for safe invocation.

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 very concise at two sentences, which is efficient, but it sacrifices necessary detail. It earns its place with minimal text but does not adequately inform the agent.

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 7 parameters, no output schema, and many sibling tools, the description is too brief. It does not explain the domain filter syntax, default field selection, ordering, or how results are returned, leaving gaps for effective use.

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%, meaning parameters like 'domain', 'fields', and 'order' have no explanations. The description adds no parameter-level information, leaving the agent to infer meaning from schema names alone, which is risky for correct usage.

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 does 'Search and read records in one call', which indicates its combined functionality. However, it does not explicitly differentiate from sibling tools like odoo_search and odoo_read, though the combination is implied.

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?

No guidance is provided on when to use this tool versus alternatives such as odoo_search, odoo_read, or other record-operating tools. The description lacks any context about prerequisites, when-not-to-use, or alternative approaches.

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