Saldos historicos

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

With no annotations, the description carries the burden and discloses meaningful behavior: automatic splitting into 60-day chunks due to the API's 64-day limit, unified series return, and summary vs. day-by-day modes. It still omits read-only status, auth requirements, and error behavior.

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 the purpose, then the chunking behavior, then return-mode guidance. Every sentence is useful and there is no redundant 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?

Without an output schema, the description does explain that it returns a summary per account by default and a daily series when detalle is true. It also explains automatic chunking, but lacks detailed output fields, auth, and error-handling context.

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 schema already documents all three parameters. The description restates the detalle meaning and adds that it returns the day-by-day series, but adds no syntax or constraints 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 resource (saldos diarios) and scope (rango de fechas largo), so the agent knows this retrieves historical daily balances. However, it does not explicitly differentiate this tool from the sibling saldos or movimientos tools.

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 phrase 'rango de fechas largo' implies when to use this tool, and 'usar detalle para la serie dia por dia' guides parameter choice. There is no explicit when-not guidance or comparison to sibling tools such as saldos or movimientos.

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