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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond that: the default cash basis, the basis change when category_id is provided, the current-month default, and bulk execution support. This meaningfully helps the agent predict behavior, though response shape and error semantics are not disclosed.

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 compact and front-loaded with the tool's core purpose. Every sentence contributes either purpose, usage context, defaults, basis behavior, or bulk support. It is dense but not bloated.

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?

The description covers critical invocation context: default period, cash basis, basis switching, and bulk parameters. However, with no output schema and zero schema-level parameter descriptions, it omits output shape, list_mode semantics, and date/parameter formats, leaving meaningful ambiguity for an agent.

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 0%, so the description carries the burden of explaining parameters. It explains category_id's effect on basis and mentions account_ids/category_ids for bulk support, but it leaves start_date/end_date formatting, list_mode values, and the relationship between account_id and account_ids undocumented. This is insufficient for a tool with 7 parameters.

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 that the tool returns financial totals for a period (revenues, expenses, result, balance, expected amounts) and positions it as a summary alternative to paginating through transactions. It does not explicitly name a sibling tool, so it stops short of full differentiation, but the purpose is unambiguous.

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 provides concrete ideal-use examples ('quanto gastei esse mês?', 'qual meu saldo?'), defaults such as current month and cash basis, and an explicit warning not to reconcile different bases. It does not name alternative tools like organizze_get_balances or organizze_get_financial_summary, so when-not-to-use guidance is implicit rather than explicit.

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