listar_lancamentos_bancarios

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

No annotations exist, so the description must disclose behavior. It only states the list action without mentioning pagination, read-only nature, ordering, or any side effects. This is insufficient for a tool with 8 optional parameters.

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 clear sentence, front-loaded with the action, and contains no fluff. However, it sacrifices important details, so it's concise but under-specified.

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?

Given the tool's complexity (8 parameters, no annotations, no output schema, many siblings), the one-line description is incomplete. It lacks information on return format, filtering, sorting, and usage alongside other tools.

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 has 0% description coverage, and the description does not elaborate on any of the 8 parameters (dates, account code, pagination, ordering). The agent receives no help understanding what values to pass.

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 'Lista lançamentos/transações bancárias em conta corrente' (Lists bank entries/transactions in current account). It specifies the verb (lista) and resource (lançamentos/transações bancárias) and scope (conta corrente). This distinguishes it from sibling 'consultar_lancamento_bancario' which implies retrieving a single record.

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 context is provided. The description doesn't explain when to use this tool over alternatives like 'pesquisar_lancamentos_financeiros' or 'consultar_extrato_bancario', nor does it mention any filters or options like date ranges or account codes.

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