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

Annotations already declare readOnlyHint and idempotentHint, establishing safety. The description adds a useful behavioral constraint with 'Max 15,' which likely caps the number of returned changes, and explicitly lists the allowed area filter values. This goes beyond the structured 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?

The description is concise, with the core purpose front-loaded in the first sentence. The optional filter and result limit follow efficiently, and every piece of information adds value without redundancy.

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 read-only tool with one optional parameter, the description covers the main aspects: purpose, filter values, and result limit. It does not describe the output format, but with no output schema and a straightforward info-retrieval use case, this gap is minor. The safety profile is fully covered by annotations.

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?

Although the schema has 100% coverage for the parameter description, the parameter has no enum values. The description compensates by listing valid area filters (requirements, security, frontend, orm, modules, api, functional, ecosystem), which is essential for correct parameter usage and not present in the schema.

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 states a specific verb and resource: 'Breaking and notable changes in Odoo 20.' It clearly identifies the tool's purpose and is distinct from sibling tools like einvoicing_status and list_vendors, which cover unrelated domains.

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?

Usage is implied by the purpose: the tool is for retrieving Odoo 20 changes. However, it provides no explicit guidance on when to prefer this tool over alternatives or any exclusions. The optional area filter is described, but no situational context is given.

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