odoo_search

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. It mentions that the tool returns 'record IDs' but does not disclose pagination behavior (limit/offset defaults, maximum), sorting, error handling, or whether additional fields are accessible. The description is too sparse to adequately inform the agent of side effects or constraints.

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 that conveys the core purpose without any extraneous information. It is well-structured and front-loaded, every word earns its place.

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, no output schema, and no annotations, the description is too brief. It does not explain the return format (only IDs, but what about pagination metadata?), the behavior of limit/offset/order, the role of the connection parameter, or any required permissions. The agent lacks sufficient context to use the tool confidently without consulting the schema extensively.

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 schema description coverage at 50% (only model, domain, and order have descriptions), the description should compensate by explaining parameters like limit, offset, and connection. However, it adds no parameter details. The existing schema descriptions are present but the description itself does not enhance parameter understanding beyond what the schema already provides.

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 'Search for record IDs matching a domain filter' clearly states the tool's action (search), resource (record IDs), and context (domain filter). It distinguishes from sibling tools like odoo_read (which reads records) and odoo_search_read (which returns full records) by specifying it returns only IDs. This is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives like odoo_search_read, odoo_search_count, or odoo_read. It does not mention conditions or limitations, leaving the agent without context for optimal selection among related Odoo tools.

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