Get Modelo 200 Summary (Corporate Tax — Annual IS)

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

Annotations already indicate read-only, idempotent, not destructive. The description adds specifics: it returns taxable base, deductions, etc., and mentions the filing deadline. 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?

Two short sentences in English, followed by Spanish translation, with an example. Front-loaded with key info, no unnecessary words.

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-only tool with one optional parameter and no output schema, the description is complete: it states what it does, for whom, what fields it returns, and filing deadline. No gaps.

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 schema has 100% coverage with a description for 'year'. The description adds default behavior ('defaults to last closed year') and an example, which is helpful 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 precisely states the tool retrieves a summary of the Modelo 200 annual corporate income tax return for Spanish SLs and SAs, listing specific fields. It clearly differentiates from sibling tools like get_modelo_130_summary (quarterly) or frihet_modelo_202_summary (installment payments).

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 includes the filing deadline and example, implying when to use it (e.g., to check tax filing status). It does not explicitly state when not to use it or list alternatives, but the context of other modelo tools provides differentiation.

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