obter_resumo_financeiro

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

With no annotations, the description carries the burden, and it does add the important caveat that OMIE calculates for a single day, not a period. However, it omits whether the operation is read-only, any permission requirements, or what the response structure looks like, leaving the agent partially informed.

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 concise, consisting of two sentences with the purpose front-loaded. It adds the essential single-day nuance without wasting words or restating the tool name.

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 tool has 3 parameters and no output schema or annotations, yet the description omits parameter behavior and return value structure. While the single-day caveat is valuable, the lack of detail about the summary's composition and the flag parameters makes it incomplete for reliable invocation.

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 provides no descriptions for data, apenas_resumo, or exibir_categoria, and the description only indirectly references 'data de referência'. The boolean parameters are completely unexplained, so agents cannot determine their impact without external knowledge.

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 verb 'Obtém' (gets) and the resource 'resumo financeiro consolidado' with specific components (contas a pagar, a receber, saldo bancário). It distinguishes itself from sibling tools like listar_contas_pagar or consultar_fluxo_caixa by focusing on a consolidated snapshot for one date.

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 use when a consolidated financial summary is needed, but it does not explicitly contrast with alternatives or state when not to use it. The single-day note hints at a limitation, but there is no comparison to period-based tools or other exclusions.

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