Saldos iniciais das contas financeiras por período. data_inicio e data_fim (YYYY-MM-DD ou ISO date-time; datas simples são normalizadas). Se omitidas, usa uma janela ampla.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| data_fim | No | ||
| data_inicio | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and idempotentHint=true, which already indicate safety. The description adds that date parameters are normalized and omission uses a wide window. However, it does not explain what 'initial balance' means or if there are pagination limits.
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 sentences: one for purpose, one for parameter details. No wasted words; front-loaded with the core action. Efficient and clear.
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?
The tool has no output schema and 3 parameters with one undocumented. The description covers the date parameters well but omits return format and the account parameter. For a simple read tool, it is adequate but missing details for full autonomous use.
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. It explains data_inicio and data_fim formats and default behavior but leaves the 'account' parameter undocumented. Partial compensation for two of three parameters.
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 the tool retrieves initial balances of financial accounts by period. The name and sentence together make the purpose specific, but it does not differentiate from the sibling tool 'contaazul_get_account_balance' which could be confused.
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 guidance on when to use this tool versus alternatives like 'contaazul_get_account_balance' or 'contaazul_list_accounts'. It mentions parameter omission behavior but lacks context for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools are easily confused: person_write_create/person_write_update and sale_write_create/sale_write_update duplicate the same operation with an internal action flag, and authenticate vs connect both deal with connection setup. Also, list_accounts (company installs) and list_financial_accounts (bank accounts) have similar names but different meanings.
Naming patterns vary widely: verb_noun (create_budget, list_people) is mixed with noun_verb (contract_write, person_delete, product_write). The contaazul_ prefix is applied inconsistently, and standalone names like authenticate, connect, marketplace, and toolkit_info break the pattern. Flattened action pairs add redundant, non-idiomatic names.
With 57 tools, this server exceeds the 50+ threshold for an extreme count. The tool list is bloated with generic platform tools (authenticate, marketplace, report_bug) alongside dozens of domain-specific ones, making it overwhelming for agents to parse and select from.
The Conta Azul domain is well represented: people, products, services, sales, budgets, contracts, financial accounts, receivables/payables, settlements, charges, invoices, and transfers all have read/create/list operations, and most have update/cancel/delete. Minor gaps like product update/delete or service update exist due to API limitations, but the core workflows are covered.