search_read

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

No annotations provided, so description carries full burden. It warns that omitting fields can return large data and that limit is capped by ODOO_MAX_RECORDS. It does not explicitly state it's a read-only operation, but the tool name and description imply querying without side effects.

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?

Description is somewhat long but well-structured with 'Args' section. Each sentence adds value. A bit verbose in examples, but concise given the number of parameters.

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 complexity (6 parameters, Odoo-specific domain language) and presence of output schema, the description fully covers input parameters, their defaults, and important warnings (large fields, limit cap). No gaps.

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%, so description must add meaning. It explains all 6 parameters with examples and default behaviors (e.g., domain syntax, fields omission, limit cap). This is highly informative beyond the schema.

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 'Query records from an Odoo model' which is a specific verb+resource. It distinguishes from sibling tools like search_count (count only) and read_records (likely different operation) by implying it performs search with filtering.

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 clear context on when to use each parameter (domain, fields, limit, offset, order) with examples. However, no explicit when-not-to-use or comparison to sibling tools, but the detailed parameter guidance compensates.

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