Releer el F29 guardado

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

Annotations already declare readOnlyHint=false and idempotentHint=true; the description adds that it updates saved values, that a mismatched reading will not overwrite a good saved one, and that no range means all months. This adds meaningful mutation and safety context beyond the annotations, though it omits return and error details.

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?

Three sentences, front-loaded with purpose, followed by the safeguard and then usage/default behavior. Each sentence contributes distinct information with no filler.

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 moderate-complexity local re-read tool with full schema descriptions and rich annotations, the definition covers purpose, triggers, default scope, and safety semantics. It does not describe return values, and there is no output schema, leaving a small but real gap.

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%, so the rut/desde/hasta parameters are already well documented. The description adds the non-obvious default that omitting desde/hasta re-reads all saved months, which is useful semantic context 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?

States a specific verb 'relee' and resource 'PDF del F29 guardados', and explicitly contrasts with 'sin ir al SII', so an agent can distinguish it from SII synchronization tools. It also clarifies the effect: re-reads each folio's PDF and updates values if they change.

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?

Gives explicit triggers: after updating mi-sii-mcp or when a saved F29 reading does not reconcile. It also states the default scope ('sin rango relee todos los meses guardados'), though it does not explicitly name a sibling alternative.

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