es__submit_sii_batch

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

No annotations are provided, so the description carries the full burden. It discloses that the tool requires MTLS certificates and sends a batch, implying a write operation. However, it does not clarify whether the submission is synchronous or asynchronous, what happens on success/failure, or any side effects. The max batch size is a useful behavioral detail, but overall transparency could be improved.

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 sentence that front-loads the action and key limit, then lists requirements. Every word is essential. There is no redundancy or unnecessary detail.

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 covers the core purpose, input limits, and authentication requirements, which is adequate for basic invocation. However, it lacks details about output (no output schema) and behavioral aspects like error handling or idempotency, which would be important for a submission tool. Given the complexity (3 params, no annotations), a bit more context would make it fully complete.

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 67% (2/3 parameters have descriptions). The description adds value by specifying the maximum number of records (10,000) for the 'records' parameter, a constraint not in the schema. This compensates for the lack of full parameter descriptions. However, it does not explain the 'record_type' enum or provide additional context for 'fiscal_year' beyond what the schema states.

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 the tool sends a batch of invoices to the AEAT SII SOAP endpoint with a maximum of 10,000 records. It includes prerequisite environment variables and certificate requirements. While it doesn't explicitly differentiate from sibling tools, the specific mention of SII batch submission makes its purpose distinct enough.

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 provides essential usage prerequisites (AEAT_ENV, certificate path/password) and a limit (max 10,000 records), but it does not offer guidance on when to use this tool vs. alternatives like es__submit_ticketbai. There are no explicit when-to-use or when-not-to-use statements.

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