Get Modelo 303 Summary (IVA Quarterly)

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is clear. The description adds valuable behavioral context: returns aggregated totals by tax rate, deductible IVA, net amount due, and filing deadline.

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?

Two sentences front-loaded with purpose, plus a bilingual repetition. The structure is efficient, though the Spanish duplicate adds minor verbosity without reducing clarity.

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 simple parameter set, high schema coverage, and presence of output schema, the description sufficiently explains what the tool returns. No missing critical details for a read-only retrieval tool.

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% with period description. The description adds an explicit example and notes acceptable formats (YYYY-QN or YYYY), enhancing usability beyond the schema.

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 it gets IVA quarterly summary for Modelo 303 filing in Spain, specifying the resource and action. The example 'period='2026-Q1'' reinforces clarity. The title and name differentiate it from sibling modelo tools.

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 usage for quarterly VAT summary but does not explicitly state when to use this tool over alternatives like other modelo summaries. No when-not-to-use or alternative references.

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