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

The description discloses the critical behavioral trait: this is an UPSERT, not a patch, so the record is written with exactly what is sent and fields meant to be preserved must be included. It also explains the important ability to modify already-settled/paid titles without canceling the payment, which goes well beyond what the annotations provide.

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 dense and front-loaded: the first sentence states core purpose, and each following line adds operationally important context. The warnings about upsert semantics, preserving fields, and settled-title behavior are all necessary; there is no filler.

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 batch upsert with no output schema, the description covers the key aspects: purpose, payload shape, read-first instruction, partition keys, and behavior on paid titles. The main gaps are the meaning of the optional `account` parameter, a more complete nested item structure, and expected response/error details.

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%, and the description compensates by explaining that `data` is a JSON string with the shape `{"lote": 1, "conta_pagar_cadastro": [...]}` and by naming the key fields `codigo_lancamento_integracao` / `codigo_lancamento_omie`. However, it does not explain the `account` parameter or the nested item fields, so parameter guidance is incomplete.

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 what the tool does: 'Cria OU atualiza VÁRIAS contas a pagar numa chamada' and names the underlying operation (UpsertContaPagarPorLote). It also distinguishes itself by saying it is the path for mass changes rather than one call per title.

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?

It explicitly describes when to use it: for batch/mass changes such as changing categories or checking accounts, and tells the agent to read data first with omie_list_payables/omie_get_payable. It does not explicitly name the single-item alternatives or state when not to use it, so some exclusion guidance is missing.

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