olist_nota_fiscal_emitir

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Esta operação altera dados' and 'exige confirmar=true', which transparently warns about the mutating nature and the confirmation requirement. However, it does not elaborate on side effects, reversibility, or permissions, leaving some behavioral gaps.

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, with three sentences that front-load the purpose, provide a documentation link, and state the key mutation safety warning. It avoids fluff and is appropriately sized, though the first two sentences ('Emitir Nota Fiscal API 2.0' and 'Endpoint API V2: nota.fiscal.emitir') are slightly redundant.

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 5-parameter mutation tool with no output schema and no annotations, the description is insufficiently complete. It lacks workflow context, prerequisites, expected outcomes, or guidance on when this operation should be used relative to other invoice-related tools. The documentation link helps but does not substitute for inline context.

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?

The input schema has 100% description coverage for all 5 parameters, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema; it only reiterates the confirmar requirement, which is already enforced by the schema's const and required fields.

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's function: 'Emitir Nota Fiscal API 2.0' (issue invoice API 2.0). It identifies the specific endpoint and resource, making the purpose unambiguous. However, it does not explicitly differentiate this 'emitir' operation from sibling invoice tools like 'incluir' or 'gerar_nota_fiscal_pedido', so it lacks explicit sibling distinction.

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. The description mentions that the operation alters data and requires confirm=true, which is a safety prerequisite but not a usage guideline. No alternatives or contextual triggers are provided.

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