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

Annotations already mark this as read-only and idempotent, and the description reinforces this with 'Não existe escrita no financeiro'. It adds rich behavioral detail beyond annotations: date_field changes which date is filtered, entry date means due date for open items, payment date only returns paid items, and batch get reports errors per id. No contradiction with annotations.

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 long but well structured with an opening summary, an 'Ações' section, a use-case sentence, a return-value summary, and a final read-only note. The list action documentation is partly extraneous given the '[Flattened action: get]' marker, but it still helps contextualize the module. Overall, nearly every sentence contributes useful information.

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 13-parameter tool with no output schema and no parameter descriptions in the schema, this description is unusually complete. It explains pagination, date filtering semantics, batch behavior, and even describes the returned shape (value, retained taxes, category, bank account, linked invoice, recipient, cost-center allocation). The main gaps are the unexplained 'account' parameter and a bit more detail on how filters combine, but these are minor given the overall coverage.

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 carries the burden for 13 parameters. It explains from/to as AAAA-MM-DD with a 366-day max, limit/offset defaults and caps, the filter parameters, entry_ids batch semantics, and date_field in depth. However, the 'account' parameter is not mentioned, and some filter parameters like dre_indicator and destination_id get only passing mention without more semantic detail.

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 opens with a specific verb and resource: 'Lê os lançamentos financeiros do iClips'. It enumerates the scope (entradas, saídas, em aberto) and distinguishes the 'get' action as returning full detail by entry_ids. This clearly separates it from the sibling 'list' tool and from other financial modules.

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 concrete usage guidance: date range constraints, default/max limit, offset pagination, filters, and the important use case for month-due entries using type='A Pagar'/'A Receber' with date_field='entry'. It does not explicitly contrast with the sibling iclips_financial_entries_list, but the get/list action split within the description makes the intended usage reasonably clear.

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