pesquisar_lancamentos_financeiros

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool searches both payables and receivables, but omits important behaviors such as pagination, filtering semantics, sorting, date range handling, or return format. This is a significant gap for a search tool with 10 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?

Two short sentences, no filler. The first sentence states the core action and scope, and the second provides practical guidance. Every word earns its place.

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?

For a tool with 10 filter parameters and no output schema, the description is too thin. It does not describe pagination controls, available filters, or the shape of results. The sibling context clarifies its niche, but the description alone leaves the agent without enough information to use the tool confidently beyond basic 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?

Schema description coverage is 0%, so the description must compensate, but it does not. It adds no details about parameter meaning beyond what the raw schema already shows. The mention of 'contas a pagar + a receber' hints at the 'natureza' parameter but does not explain any of the other filters or their acceptable values.

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 verb 'Pesquisa' clearly indicates a search action, and the resource is specified as 'lançamentos financeiros' (financial transactions). The explicit scope 'unificada (contas a pagar + a receber)' distinguishes it from sibling tools like listar_contas_pagar and listar_contas_receber, which address each type separately.

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 states 'Ideal para visão consolidada das finanças', providing clear context for when to use this tool: when a consolidated view of payables and receivables is needed. It implies the alternative of using separate list tools for each type, though it does not explicitly name alternatives or state when not to use it.

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