search_records

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description only echoes that read semantics via 'return the matching rows.' It adds nothing about pagination, the default 100-row cap, or behavior when limit is omitted, which are the operationally relevant traits for a search tool.

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?

One sentence, zero filler, with the action and the return stated up front. It is efficient rather than padded, though its brevity borders on under-specification for a six-parameter tool.

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?

For a six-parameter search with one required field and no output schema, the description leaves major gaps: pagination via limit/offset, default row cap, field-selection guidance, and behavior on an invalid domain are all unaddressed. Annotations cover only the safety profile, so the description should carry far more of this burden.

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 83%, so the schema already documents model, domain, fields, order, and limit syntax. The description only restates 'Odoo domain' and adds no format or default guidance beyond the schema; baseline 3 applies.

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?

Specific verb+resource (search records) with the mechanism named (Odoo domain) and the return subject stated (matching rows). It is clear what the tool does, but it never differentiates itself from siblings like search_count or name_search, which sound nearly identical to an outside reader.

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 when-to-use, when-not-to-use, or alternative is given. An agent must infer that search_count is for totals and name_search is for name lookups; the description provides no routing signal at all.

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