odoo_search_read

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

No annotations are present, so the description carries the full burden. It discloses behavior like 'Empty/omitted matches all records (subject to record rules)' and default limit of 80, which are meaningful. However, it does not mention offset behavior or return format, leaving some gaps.

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 compact and front-loaded, beginning with a clear one-line purpose followed by a concise parameter list. Every line provides useful information with no redundancy or fluff.

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's generic nature and absence of output schema/annotations, the description covers essential aspects like domain semantics, limits, and ordering. It lacks a note about return value structure and offset, but the core usage is well covered for most scenarios.

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 coverage is 0%, and the description compensates by explaining model, domain, fields, limit, and order with examples. It omits offset semantics, which is a minor gap, but overall it adds significant meaning beyond the schema's bare property names.

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 'Search and read records of ANY Odoo model in one call' with a clear verb and resource scope. It differentiates from siblings by emphasizing generic model access, unlike specialized tools like search_invoices or search_budget_lines.

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 clarifies that it works for any model, implying use when a dedicated tool is absent, but does not explicitly exclude alternatives. It provides practical parameter guidance, such as 'limit 0 for no limit -- careful on large models', which helps agents decide when to use it.

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