olist_nota_fiscal_lancar_contas

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

The description states 'Esta operação altera dados e exige confirmar=true', but this largely duplicates the schema's confirmar parameter description (which already says 'operação mutável' and const true). No new behavioral traits are added, such as side effects, reversibility, permissions, or what happens to existing data. With no annotations, the description fails to carry the behavioral burden.

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 short but not optimally structured. It begins with a fragment that restates the tool name, then includes endpoint and documentation URL, and finally a behavioral sentence. The endpoint and URL are somewhat redundant noise for an agent, making it less concise than a clean two-sentence description.

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 lack of output schema and annotations, the description should explain what the operation does, what it returns, and when to use it. It does none of these. It also fails to differentiate from similar tools like olist_pedido_lancar_contas. The provided endpoint and docs link are helpful but not sufficient for an agent to fully understand the operation's effect.

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 coverage is 100%, with both id and confirmar having clear descriptions. The tool description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 applies.

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 identifies the tool as 'Lançar Contas da Nota Fiscal' (launch accounts for fiscal note), which is a specific verb+resource. It distinguishes from siblings like olist_nota_fiscal_lancar_estoque by using 'contas' vs 'estoque'. However, it does not fully elaborate what 'lancar contas' entails, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, use cases, or exclusions. The only contextual hint is that it alters data and requires confirmar=true, which is more about behavior than usage selection.

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