Get Modelo 202 Summary (Corporate Tax — Installment Payments)

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by specifying return fields (installment amount, due date, status, cumulative total vs projection) and the optional installment parameter. This provides behavioral context beyond the annotations, but does not cover potential errors or prerequisites.

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 very concise yet informative, with bilingual sections (English and Spanish) that are each one sentence plus an example. Every sentence adds value, and key information is front-loaded.

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 tool is read-only with no output schema, the description adequately explains what is returned (amounts, due date, status, cumulative total). It covers the two parameters and optionality. Minor gaps: no mention of authentication requirements or error conditions, but for a summary tool it is complete enough.

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 descriptions for both parameters. The description adds meaning by explaining that the 'installment' parameter can be omitted to get all three, clarifying the enum values, and providing an example (year='2026', installment='1P').

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 'Get Modelo 202 summary — installment payments for Corporate Tax' and enumerates the three installments, returned fields, and includes an example. It distinguishes itself from sibling modelo summary tools by specifying the exact tax 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 explains what the tool is for (Modelo 202 installment payments) and the context of three annual payments. However, it does not explicitly state when not to use it or contrast with alternatives, though sibling names imply uniqueness.

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