Get Modelo 180 Summary (IRPF Rentals Annual)

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the return structure (retentions per tenant, property, annual aggregate) but does not disclose additional behavioral traits such as rate limits or authentication requirements.

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, with two sentences in English followed by Spanish translation. It front-loads the purpose and includes an example, with no extraneous content.

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 one optional parameter, rich annotations, and an output schema (not shown), the description adequately explains the tool's functionality. It mentions return aggregates but does not explicitly state that the period is optional (though schema coverage implies it). Minor gap for full completeness.

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 covers the single 'period' parameter with 100% description coverage, specifying the YYYY format. The description provides an example ('period='2025'') which adds marginal value but does not significantly expand on 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 the tool retrieves the IRPF annual informative summary for rental income withholdings (Modelo 180, Spain), specifying the returned data (retentions per tenant, property, annual aggregate). The title and example further clarify the scope, distinguishing it from other modelo summaries.

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 Modelo 180 via the title and tax form name, but does not explicitly state when to use this tool versus alternatives like get_modelo_130_summary. With many sibling tools, explicit guidance on selection would improve clarity.

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