sii_mipyme_list_empresas

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

There are no annotations, so the description carries the behavioral disclosure burden. It correctly frames this as a read-only listing action and mentions the authentication scope ('persona autenticada'). It does not describe return format or pagination, but for a simple no-parameter listing tool the verb 'Lista' sufficiently conveys non-mutating behavior.

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, efficiently written sentence that front-loads the core action and result scope, then adds essential usage timing. Every word contributes value with no 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 no parameters, no output schema, and a simple list operation, the description fully covers what the tool does, the system and scope, and when to invoke it. It is complete in context, especially as a discovery step before DTE-related 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?

The tool has zero parameters, so the schema is empty and the description need not explain any parameter semantics. Baseline 4 is appropriate since there is nothing to clarify and no mismatch.

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 ('Lista') and a clear resource ('empresas que la persona autenticada puede operar'), and identifies the exact system (SII free invoicing, mipyme.sii.cl). This clearly differentiates it from sibling tools that list DTEs or properties.

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 explicitly states when to use: 'Usar antes de otras tools cuando SII_EMPRESA_RUT no está configurado.' This gives a concrete precondition and implies that when the environment variable is configured, this tool is not needed. It serves as a discovery/prerequisite step without needing to name alternatives.

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