Generic read-only query on Odoo.sh models

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description repeats read-only without adding safety details like auth, limits, or error behavior. It adds the whitelisted/escape-hatch framing but does not go beyond the annotations meaningfully.

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?

Two tight sentences with no filler; the example is embedded compactly. Front-loads the verb and resource, then gives the when-to-use cue.

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?

Enough for a generic read-only escape hatch: model enum, domain example, field list, and limit default are available. It doesn't state return shape or error behavior, but that is less critical for a simple search_read.

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 covers most parameters; the description adds a concrete domain example and clarifies fields vs domain, but limit and order semantics are left to the schema. Since coverage is high, this is above baseline but not thorough.

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?

Clearly states it runs a search_read on whitelisted Odoo.sh models and positions itself as a generic read-only escape hatch. The example domain makes the intended use concrete, and the contrast with curated tools distinguishes its purpose.

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?

Explicitly says to use it when curated tools don't cover a need, which is a clear selection condition. The example domain also gives concrete usage guidance.

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