olist_nota_fiscal_lancar_estoque

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

The description discloses that the operation 'altera dados' (mutates data) and requires confirmar=true, which is useful beyond the schema. However, with no annotations, it carries the full burden and does not explain what 'lançar estoque' does in practice, side effects, or whether it is reversible.

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 concise and front-loaded with the main purpose, then endpoint, documentation, and mutation warning. It contains no redundant fluff, though the structure could be slightly improved by separating the warning into its own sentence (it already is).

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 simple tool with 2 parameters and no output schema, the description is minimally adequate, providing mutation semantics and confirmation requirement. However, it lacks information about return values, expected behavior, or prerequisites (e.g., the invoice must exist), which would be crucial for a mutation tool.

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 100%, so the baseline is 3. The description adds minimal semantic value beyond the schema: it repeats the confirmar=true requirement but does not explain the 'id' parameter beyond what is already in the schema.

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 ('Lançar Estoque da Nota Fiscal') and identifies the resource, but it does not differentiate this from sibling tools like olist_pedido_lancar_estoque or olist_nota_fiscal_lancar_contas. The endpoint name and doc link reinforce but do not add distinct purpose clarity.

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 explicit guidance on when to use this tool versus alternatives. It provides an endpoint and documentation link but does not state prerequisites, scenarios, or exclusions. The mutation warning is generic and not tied to use cases.

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