Emitir NFS-e

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

Annotated with openWorldHint and idempotentHint. Description adds significant context: confirmation requirement, mode effects (mock in sandbox, certificate in production), idempotency key, block processing, side effects (saves PDFs/XMLs, updates CSV). No contradictions with annotations.

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?

Three dense sentences covering purpose, behavior, and key constraints. No redundancy; every sentence adds value.

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?

Covers emission, modes, idempotency, block processing, and side effects. Mentions return progress but lacks detailed output structure. Without output schema, this is a minor gap; overall sufficient for a complex 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 covers 5 of 6 parameters (competencia missing description). Description adds meaning: confirmar as safety lock, modo override constraints, offset resume, apenasLojas restriction, tamanhoBloco default. Complements schema well.

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?

Description clearly states the purpose: emit NFS-e for a given period (competência) per store. It differentiates from sibling tools like preview or status, and specifies the verb 'emite' and resource 'NFS-e'.

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?

Provides guidance on when to use (actual emission), required confirmation flag, mode behaviors (dry-run, sandbox, production), idempotency, and block processing. However, explicit contrast with preview tool could be stronger.

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