Estado de resultados de institución financiera

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

The annotations already declare the operation as read-only and non-destructive. The description adds useful context by specifying the monthly granularity and the special meaning of institucion=999, but it does not disclose any additional behavioral details such as response formats or rate limits, which are less critical given the output schema and read-only annotation.

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 short sentences, front-loaded with the core purpose and a key parameter tip. No redundancy or extra verbosity.

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 read-only query tool with an output schema and three parameters, the description conveys the essential information: what data is returned, the granularity, and a special parameter value. It does not explain return structure, but the output schema covers that.

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?

The schema has no descriptions for the three parameters, and the description only explains the special value 999 for 'institucion'. It does not elaborate on the general meaning of the institution code or the format of mes/anio, though the regex patterns provide some guidance. This is partial compensation for the low schema coverage.

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 the monthly income statement ('Estado de resultados mensual') for financial institutions from the official v3 API, distinguishing it from sibling tools like balance or ficha. However, it lacks an explicit action verb, relying on the noun phrase to convey 'gets'.

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 provided on when to use this tool versus related tools such as cmf_api_balance_institucion. The only usage hint is the special value 999 for the total financial system, which is more about parameter input than tool selection.

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