Memoria anual

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds minimal behavioral context by specifying that the result is the annual report for an issuer/year, but it does not disclose auth needs, rate limits, or response behavior beyond what the annotations and output schema already imply.

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 a single, front-loaded sentence with no redundant wording. It conveys the essential purpose and scope immediately, though 'pestanía 49' is slightly cryptic but not wasteful.

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 two-parameter read-only tool with an output schema, the description is minimally sufficient to identify the resource. However, it does not clarify parameter relationships or explain the cryptic 'pestanía 49' reference, leaving some contextual 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?

With 0% schema description coverage, the description must compensate, but it only loosely maps 'emisor' to rut and 'año' to anio. It does not explain optionality (no required params), value formats beyond the regex, or how to use the two parameters together.

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 resource ('memoria anual de un emisor') and the temporal scope ('para un año'), which distinguishes it from financial statements or events among sibling tools. However, it lacks an explicit verb like 'obtiene/retrieves', so it falls short of the strongest purpose statements.

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?

No guidance is given about when to use this tool instead of related cmf_empresa_* tools, nor are any exclusions or prerequisites mentioned. The phrase 'para un año' implies a filtering use case but does not constitute actionable usage guidance.

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