emitir_nfe

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the requirement for complete JSON data, but does not mention authentication needs, potential side effects, idempotency, success/failure indicators, or response behavior. The mutation nature is implied by 'emite' but not elaborated.

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, succinct sentence that leads with the action and then states the key requirement. No filler or redundancy, making it easy to parse quickly.

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?

The tool is simple with one parameter, but the absence of an output schema and annotations means the description should clarify return values or permissions. It does not, and while the core purpose is clear, the description is not fully complete for a production usage 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?

Schema coverage is 100% as the only parameter 'dados' has a detailed description covering the JSON structure and typical fields. The tool description adds minimal extra meaning (emphasis on 'completeness') beyond the schema, so the baseline score of 3 for high schema coverage is appropriate.

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 opens with 'Emite uma nova Nota Fiscal Eletrônica (NF-e)', which is a specific verb (emite) plus resource (NF-e), clearly distinguishing it from sibling tools like cancelar_nfe or baixar_pdf_nfe. The addition of 'nova' and the requirement for complete JSON data further disambiguates this as the creation tool.

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 implies usage when you need to issue a new NF-e and have complete data, but it does not explicitly mention alternatives or when not to use the tool. Sibling tool names provide contextual contrast, but the description itself lacks explicit guidance or exclusions.

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