es__generate_verifactu_record

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

Describes output (XML and hash for chaining) and discloses chaining mechanism. However, no annotations are provided, and the description omits details on idempotency, error conditions, side effects, or authentication requirements, leaving behavioral gaps.

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?

Two concise sentences in Spanish, front-loaded with the core action and output. Every sentence adds value with no redundancy or 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?

Covers prerequisite call and output (XML, hash). For a generating tool with 8 parameters, nested objects, and no output schema, the description provides minimal but adequate context for usage. Could elaborate on output structure or error handling, but it is reasonably complete given sibling 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 description coverage is 100%, so baseline is 3. The description does not add meaning beyond what the schema already provides for each parameter (e.g., invoice, previous_hash). No additional parameter context is given.

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?

Description clearly states verb (generates) and resource (VERI*FACTU record with SHA-256 hash chain), specifies regulation (Orden HAC/1177/2024), and mentions output (XML and hash). Distinguishes from siblings like cancel and validate.

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?

Explicitly advises calling es__detect_regional_regime beforehand, providing a clear usage prerequisite. Does not enumerate alternatives or when-not-to-use, but context is sufficient for correct invocation.

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