Fuentes oficiales de datos públicos

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

Annotations already cover the safe read-only profile, and the description adds important context: mi-sii-mcp does not store these public data and the tool does not go to the SII. It also explains what the tool returns (where to consult and what to search, plus the F22 rule when regla=true), though it does not discuss data freshness or update cadence.

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 dense but front-loads the core distinction: these are public data the server does not store, and the tool points to official sources. The long parenthetical list is useful for scope but makes the opening sentence heavy.

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 two-parameter reference tool with full schema coverage, no output schema, and annotations already declaring read-only behavior, the description is largely complete: it explains the data categories, the official sources, the optional rule, and how it relates to renta_resumen. It is slightly incomplete on freshness/versioning of the referenced rates and tables.

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 description coverage is 100%, so the schema already documents both parameters. The description adds some meaning for regla=true by specifying a step-by-step F22 estimate for a person with salary and honorarios, but it does not add information about the buscar filter 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?

It clearly states a specific purpose: a guidance/reference tool that tells which official page to consult for each public tax/social-security datum and what to search there, with an optional step-by-step F22 rule. It explicitly distinguishes itself from sibling renta_resumen by assigning private data there and public data here.

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 gives explicit timing and routing: use it before estimating income, private data comes from renta_resumen, public data from the named official pages, and the year calculated determines the figures. It also states a clear exclusion: 'No va al SII.'

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