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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds that records are not downloaded (a lightweight/aggregate behavior), but says nothing about permissions, the cost of large domains, or the shape of the returned count — though an output schema exists to cover returns.

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?

A single five-word sentence with zero waste, front-loading the verb and the key differentiator ('sin descargarlos'). Nothing is padded or redundant.

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?

With annotations covering safety and an output schema covering the return value, the description needs only to establish purpose and routing. It covers purpose minimally but omits the routing signal to odoo_search_read that an agent with 11 sibling Odoo tools would need, leaving the definition adequate rather than complete.

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 100% — 'model' and 'domain' are both documented as 'Modelo Odoo.' and 'Dominio de búsqueda.' — so the schema carries parameter meaning. The description adds nothing about the model string format or domain filter syntax, so 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?

States a specific verb (count) and resource (records), and the clause 'sin descargarlos' implicitly separates it from odoo_search_read, which returns full records. It never names the sibling it is contrasted with, so the differentiation is inferable rather than explicit.

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 phrase 'sin descargarlos' hints at the use case (need a number, not the data), but there is no explicit when-to-use statement or reference to odoo_search_read as the alternative for retrieving records. Usage must be inferred from the description's implication.

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