Listar Cambios

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds the scope of the listing (project and global memory), which is somewhat useful but does not disclose any other behavioral details such as ordering, pagination, or default inclusion of both memory types (though that is in the schema).

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?

One concise sentence that immediately conveys the function with no fluff.

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?

The description is brief but adequate for a simple read-only list operation, especially with the schema providing parameter details and annotations declaring safety. However, it lacks any usage guidance or mention of output format, and does not clarify when to prefer this over sibling search/relevant-change tools.

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 already describes 3 of 4 parameters (limit lacks description but has type/min/max). The description does not add meaning beyond saying the changes come from project and global memory, which matches includeProject/includeGlobal. Thus it adds little beyond 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 clearly states the tool lists changes saved in project and global memory (verb 'Lista' + resource 'cambios guardados'). This distinguishes it from siblings like search_changes (search) and get_change (retrieve specific change).

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 provides no guidance on when to use this tool vs alternatives like search_changes or get_change. It only states what it does, without any exclusions or recommendations.

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