Cria um produto (nome + valor_venda obrigatórios em data JSON). A API v2 do Conta Azul não expõe atualização nem GET de produto por id — para consultar, use contaazul_list_products (/produto/busca) com filtro.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| account | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds critical context: the Conta Azul API v2 does not expose update or GET-by-ID for products. This clarifies that creation is the only write operation and that products cannot be individually retrieved later. 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 extremely concise with only two sentences. The first sentence directly states purpose and required fields. The second sentence adds essential contextual information about API limitations and a sibling alternative. No unnecessary words.
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's simplicity, lack of output schema, and annotations, the description covers: purpose, required fields, API limitations, and an alternative tool. It is mostly complete but could mention the response format (e.g., whether it returns an ID) or potential errors.
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 by explaining that the 'data' parameter must be a JSON containing 'nome' and 'valor_venda' as required fields. This adds semantic meaning beyond the schema's simple 'string' type. However, the 'account' parameter is not explained.
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 creates a product and specifies required fields ('nome' and 'valor_venda') in the 'data' JSON. It also distinguishes itself from sibling tools by noting that the API lacks update and get-by-ID endpoints, directing users to 'contaazul_list_products' for queries.
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 explicitly tells when to use this tool (to create a product) and when not to (for updates or retrieval, as the API doesn't support them). It provides a clear alternative: use 'contaazul_list_products' with filters for querying products.
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.