sii_mipyme_emitir_dte

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

With no annotations provided, the description carries the full burden. It discloses the mutating nature ('Emite') and the return value ('Devuelve el folio asignado'), but does not mention authentication requirements, session prerequisites, or the permanence of the emission. This lacks the depth expected for a mutation tool.

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 two sentences, front-loaded with the verb, and every clause serves a purpose. No filler or 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?

Given the 5-parameter schema covers all inputs and the description mentions the return value, the tool is mostly complete. However, it lacks guidance on authentication state or that the emission is a final submission to SII, which would be helpful in the broader SII tool context.

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 schema already documents all parameters. The description adds a useful clarification that RUT and DV are separate, but no other parameter semantics beyond the schema. This aligns with the baseline for high schema coverage.

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 uses a specific verb 'Emite' with a resource 'DTE' and clearly names the system (mipyme.sii.cl). It distinguishes from sibling list/get tools by indicating this is the emission tool, and even provides examples of DTE types.

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?

It clearly states that RUT and DV must be provided separately, giving necessary usage context. However, it does not explicitly mention when to use this tool versus alternatives or provide exclusions, though sibling names make the distinction apparent.

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