Get Modelo 303 Summary (IVA Quarterly)

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe read operation. The description adds value by explaining the output structure (aggregated totals, deadlines) and usage context (Spanish IVA quarterly filing), which is beyond the annotations. No contradictions with annotations.

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 in English followed by the same in Spanish. It is front-loaded with the verb and resource. The duplication makes it slightly longer than necessary, but it serves a bilingual audience. Every sentence adds value.

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 complexity (single parameter, output schema exists), the description adequately explains the tool's purpose and return values. It does not need to cover return values since output schema is present. The explanation of fields and deadline is sufficient.

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 input schema covers 100% of the parameter 'period' with format description. The description provides an example ('2026-Q1') but does not add significant meaning beyond the schema. Baseline 3 is appropriate given 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 clearly states the tool gets a quarterly IVA summary for Modelo 303 filing in Spain, listing the specific fields returned (totals by tax rate, deductible IVA, net amount due, filing deadline) and providing an example. This distinguishes it from siblings like get_modelo_130_summary (different form).

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 implies use for Modelo 303 filings but does not explicitly state when to use this tool over alternatives like get_modelo_130_summary or get_monthly_summary. No when-not or exclusion criteria are provided, though the form number and quarterly nature are clear.

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