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

Beyond the read-only/idempotent annotations, it discloses that Open Finance raw details are omitted, that cashflow mode hides paid credit-card invoices and individual card expenses, that truncated pages must not be summed, and exactly how 'paid' should be interpreted for manual vs automatic accounts. This is rich behavioral disclosure.

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?

Long but well organized with uppercase section labels (PAGINAÇÃO, TOTAIS, LIMITE, INTERPRETAÇÃO DO STATUS) and every block carries a distinct operational warning. The purpose statement is front-loaded before advanced nuances.

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 complex 13-parameter tool with no output schema, it covers pagination, totals semantics, mode-specific visibility, limit guidance, paid/pending interpretation, and bulk support. Minor gaps like order_by values and exact response shape are non-critical to calling it 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?

With 0% schema description coverage, the description compensates for many parameters: page/per_page caps, list_mode values with default and auto-switch via category_id, and bulk account_ids/credit_card_ids/category_ids. However, order_by and installments_only are left unexplained, and singular vs bulk id parameters are only implicitly covered.

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?

Opens with a specific verb and resource ('Lista transações do usuário no período selecionado') and immediately scopes pagination with a page size cap. It also contrasts with get_transaction for full records and with reporting tools, so an agent can distinguish list from detail/report operations.

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?

Explicitly tells when to choose all_transactions vs cashflow, when to use category_id, and when to prefer get_transaction or get_categories_report/transactions_list_results. It also instructs to narrow filters when truncated or when the period is too large, giving strong routing guidance.

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