Obtener Cambio

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

Annotations declare readOnlyHint=true, so the read-only nature is already communicated. The description adds that the retrieval is 'exacto' (exact) by id, but it does not disclose behavior when the id is not found, return format, or how includeGlobal/includeProject affect the lookup.

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 a single, front-loaded sentence that immediately expresses the core functionality with no filler or redundancy. It efficiently uses the available space.

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 no output schema, the description should explain what a 'cambio' contains or what happens on failure, but it does not. The optional memory-related parameters are entirely omitted from the description, leaving their behavior solely to schema definitions, which is insufficient for a complete understanding.

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 description clarifies that the 'id' parameter is the change's identifier, which is missing from the schema description for id. However, the other three parameters (projectPath, includeGlobal, includeProject) already have detailed schema descriptions, so the description adds minimal value beyond that.

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 'Recupera un cambio exacto por id' clearly states the action (retrieves), the resource (a change), and the identifier used for retrieval. This distinguishes it from sibling tools like list_changes or search_changes, which operate on collections or queries.

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 'por id' implies that the tool is for retrieving a specific known change by its identifier, but it does not explicitly compare against alternatives like search_changes or list_changes. No exclusions or when-not-to-use guidance is provided, leaving usage context implicit.

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