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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds the key behavioral detail that it counts without downloading records, which goes beyond the annotation and clarifies that no data payload is returned.

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, concise sentence that fully conveys the tool's purpose without unnecessary words. It is front-loaded and efficient.

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 simple count operation with a readOnly annotation and an output schema, the description is sufficient. It does not explain edge cases or domain syntax, but the schema covers parameter format, and the output is likely a number, so completeness is adequate.

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% with both 'model' and 'domain' having short descriptions. The tool description adds no additional parameter context, so it rests on the baseline for fully described schemas.

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 'Cuenta registros sin descargarlos' clearly states the action (counting records) and distinguishes it from sibling tools like odoo_read or odoo_search_read, which fetch data. It specifies the resource (records) and the behavior (without downloading).

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 implies use for counting without fetching, but does not explicitly mention when to prefer this over search_read or list_models. It lacks explicit 'use this instead of' or alternative conditions, though the purpose is intuitive.

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