excluir_conta_pagar

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

With no annotations, the description carries the full burden. It discloses the destructive nature ('Exclui') and the open-title constraint, which are useful. However, it lacks details about irreversibility, required permissions, or effects on related records, leaving significant behavioral gaps for a delete operation.

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 a single sentence that immediately states the primary action and the conditional scope. Every word adds value, with no filler or repetition.

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 deletion tool with no annotations and no output schema, the description is too thin. It does not explain how to identify the target, what happens after deletion, or any return/error behavior, making it incomplete for reliable agent 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% and the description does not mention either parameter. The two parameters (codigo_lancamento_omie and codigo_lancamento_integracao) are the sole means of identifying the target, and the description gives no guidance on which to use or that at least one is required, leaving the agent unable to invoke correctly.

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 action ('Exclui uma conta a pagar do OMIE') with a specific verb and resource, and includes a scope delimiter ('apenas títulos em aberto') that distinguishes this from related tools like consultar_conta_pagar or cancelar_pagamento_conta_pagar.

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 conveys a clear condition for use ('apenas títulos em aberto'), implying that closed or paid titles should not be deleted via this tool. It does not explicitly name alternatives, but the open-title restriction provides usable guidance for when to apply this tool.

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