listar_contas_receber

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

With no annotations, the description must carry the disclosure burden. It does not state that the operation is read-only, nor does it mention pagination, defaults, or any side effects. The single sentence adds no behavioral context beyond the name.

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?

One sentence, front-loaded with the core action and object. No wasted words, though it is sparse.

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 has 12 parameters, no annotations, and no output schema, this description is severely incomplete. It omits how to handle pagination, date formats, sorting, and filter combinations, making it hard for an agent to invoke the tool correctly.

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 coverage is 0%, so the description should explain the 12 parameters. It only covers status, period, and client in general terms, leaving pagination, sorting, ordering, bank account, emission dates, and the open-titles flag undocumented. This partial coverage is insufficient for an agent to set parameters correctly.

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 'Lista contas a receber' — a clear verb+resource statement that identifies exactly what the tool does. It adds filter dimensions (status, period, client), distinguishing it from siblings like listar_contas_pagar or listar_titulos_em_aberto.

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 no guidance on when to choose this tool over related queries such as listar_titulos_em_aberto, pesquisar_lancamentos_financeiros, or consultar_conta_receber. There is no mention of preconditions, exclusions, or recommended contexts.

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