Get Modelo 303 Summary (IVA Quarterly)

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

Annotations already mark it as read-only and idempotent. Description adds value by detailing return object contents (aggregated totals, deductible, net amount, deadline), compensating for no output schema details beyond 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?

Two sentences, front-loaded with English, includes Spanish translation. No fluff, but bilingual text adds minimal overhead. Efficient for the needed information.

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?

For a simple read tool with one parameter and an output schema, description covers purpose, return fields, example, and period format. No gaps; completely adequate.

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?

Single parameter 'period' is fully documented in schema. Description adds example and explains format (YYYY-QN or YYYY), enhancing understanding beyond the schema's description.

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?

Clearly states it gets the IVA quarterly summary for Modelo 303 filing, specifies return fields (aggregated totals by tax rate, deductible IVA, net amount due, filing deadline), and provides an example. Unambiguous and distinguishable from siblings like get_modelo_130_summary.

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?

Implies usage for quarterly VAT but lacks explicit guidance on when to use vs. other Modelos. No exclusions or alternatives mentioned, though the name and description provide context.

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