Export Payroll (Gestoria Format)

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

Annotations indicate read-only, idempotent, non-destructive, and closed-world. The description adds that the tool exports staged data and does not calculate payroll, which aligns with annotations. No contradictions.

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 concise and well-structured with bullet points for formats. The final Spanish sentence is redundant as the rest of the description is already bilingual. Slightly more wordy than necessary.

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 purpose, formats, date format, and what the tool does not do. Since there is an output schema, it need not explain return values. Complete for the tool's complexity.

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 coverage is 100% and parameter descriptions are already bilingual and detailed in the schema. The tool description adds minimal new info (e.g., the note about not calculating payroll) but largely repeats the schema content.

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 title and description clearly state the tool's purpose: exporting payroll data in gestoria-compatible format. It lists five specific formats and emphasizes that Frihet does not calculate payroll, distinguishing it from other payroll tools like payroll_checklist.

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 explicitly says when to use (export staged data) and what it does not do (no payroll calculation). It specifies supported formats and date format. However, it does not mention alternatives among sibling tools for when not to use this tool.

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