Cartola diaria de Fondos Mutuos

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds valuable operational context: 'Requiere captcha de la CMF: si no se entrega, la tool lo solicitará.' This discloses an authentication/verification requirement and the tool's fallback behavior. No contradiction with annotations.

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 two sentences: the first front-loads the core function and data fields, the second adds the essential captcha requirement. No filler or redundant material.

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 presence of an output schema and read-only annotations, the description covers the key operational caveat (captcha) and scopes the query to a date range and fund. It does not need to describe return values because the output schema exists.

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 only 25% (only 'fondo' is described as RUN del fondo). The description helps by indicating the tool operates over a 'rango de fechas' and that captcha may be requested, but it does not individually explain 'desde'/'hasta' or the captcha field beyond the schema's regex/length constraints.

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 identifies the tool as returning a daily cartola (valor cuota, patrimonio, partícipes) for a mutual fund over a date range, which distinguishes it functionally from sibling fund tools. However, it is a noun phrase rather than an explicit verb+resource statement, so it falls short of the strongest purpose clarity.

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 when needing daily fund data over a date range and notes the captcha requirement, but it does not explicitly state when to choose this over alternatives like cmf_fondos_mutuos_cartera or cmf_fondos_mutuos_bpr. No exclusions or alternative comparisons are provided.

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