es__cancel_verifactu_record

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool generates a cancellation record and that it is chained to the existing hash sequence, which is useful. However, it does not clarify whether this is a local generation, whether it mutates stored state, or whether any submission side effect occurs.

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 extremely concise: two short sentences, both informative. It front-loads the core purpose and then adds the chaining constraint without any filler.

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 adequate for a tool with a rich input schema and an output schema, but it lacks explicit guidance on when to use it versus siblings and does not describe behavioral side effects. For a complex VERI*FACTU cancellation workflow, slightly more context would be beneficial.

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%, so the input schema already documents all parameters clearly. The description adds no extra parameter-level meaning, but it does not need to because the schema is self-sufficient.

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 a specific action: generating a VERI*FACTU cancellation record with TipoHuella=01. It distinguishes itself from the sibling generate_verifactu_record by identifying this as an annulment record rather than a normal record.

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 usage context by noting the record is chained to the current hash sequence, which tells the agent that previous_hash must be from the latest record. However, it does not explicitly state when to prefer this tool over alternatives such as generate_verifactu_record or validate_verifactu_record.

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