consultar_extrato_bancario

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

Without annotations, the description discloses key behavior: it returns all transactions and the period balance. It also reveals the OMIE constraint requiring one of the two IDs. However, it doesn't confirm read-only behavior, error handling, or result limitations, which would be valuable given no other metadata.

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 three concise sentences, front-loaded with the primary purpose. Each sentence is purposeful: stating what it does, what it returns, and the key input requirement.

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 the core function, return type, and a key parameter constraint, but leaves gaps on date format, the meaning of exibir_apenas_saldo, and the structure of the returned statement. With no output schema or annotations, these omissions make it incomplete.

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%, and the description adds meaning only to the two ID parameters, explaining they are mandatory alternatives and how to obtain them. It does not explain data_inicio/data_fim format or exibir_apenas_saldo, leaving most parameters underspecified.

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 tool's purpose: 'Consulta o extrato bancário de uma conta corrente em um período' and specifies the return ('Retorna todos os lançamentos e o saldo do período'). This is a specific verb+resource+scope that distinguishes it from related tools like listar_lancamentos_bancarios.

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 clear usage context by requiring one of two account IDs ('Informe codigo_conta_corrente ou codigo_integracao_conta') and recommending listar_contas_correntes to discover the code. It lacks an explicit 'when not to use' or direct comparison to alternatives, but the guidance is helpful.

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