listar_lancamentos_bancarios

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

No annotations are provided, so the description must carry behavioral transparency. It only states the action without disclosing any behavioral traits such as pagination behavior, ordering, date limits, or whether the list is filtered. It also does not mention if this is a read-only operation or if any side effects exist.

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 a single concise sentence, which is efficient and easy to parse. However, it is under-specified and does not provide enough content to be fully useful. It is not overly verbose, but the brevity sacrifices necessary detail.

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?

With 8 parameters, no output schema, and no annotations, the description is far too minimal. It fails to explain the filtering, pagination, ordering, or output format. Given the tool's complexity and the rich sibling context, the description is incomplete and does not allow an agent to use it effectively.

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%, but the description offers no information about the 8 parameters (e.g., filtering by date, account, pagination). It does not compensate for the schema gap in any way. The parameter names in the schema give some hints, but the description adds no semantic value.

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 uses a specific verb 'Lista' and resource 'lançamentos/transações bancárias em conta corrente', clearly indicating the tool lists bank transactions in a checking account. It distinguishes from siblings like consultar_lancamento_bancario (single transaction) and listar_pix (PIX-specific).

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as pesquisar_lancamentos_financeiros, listar_movimentos_financeiros, or consultar_extrato_bancario. There is no context about scenarios where this specific listing is preferable.

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