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 adds genuinely new behavior: it performs no Odoo operation at all, only reads connector-level usage, and the reported window is 'este mes'. That scoping detail is useful context beyond the annotations.

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?

Front-loaded statement of what is measured, followed by the not-Odoo caveat and then illustrative user questions. Three sentences carry little waste, though the quoted example phrasings are somewhat redundant with the opening sentence.

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 an output schema present, return values need not be explained. Given zero parameters and read-only annotations, the description covers everything an agent needs: what is counted, the monthly window, and that no Odoo call is involved.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. The description correctly adds no parameter talk, which is appropriate for a no-argument tool.

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 and resource: reports how many Odoo MCP connector calls have been consumed and how many remain this month. It also explicitly separates itself from the odoo_* siblings by declaring 'No toca Odoo — solo consulta el uso del propio conector', so an agent can route correctly without opening any schema.

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?

Gives clear context for use: answer '¿cuánto llevo gastado?' or '¿cuánto me queda?' directly, without first performing an operation on Odoo. It does not name set exclusions or point at a specific alternative tool, but the scope of intended questions is unambiguous.

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