emitir_nfse

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

No annotations are provided, so the description carries the full burden. It discloses that the tool issues a new NFS-e (a write operation) and requires complete JSON data, but it does not mention side effects, authentication, reversibility, or response behavior.

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?

Two short sentences, front-loaded with the core purpose and a concise requirement. Every word 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?

Given the simple schema (one param, no output schema) and the absence of annotations, the description covers the basics. However, for a tool that issues a legal tax document, it omits important context about consequences, authorization, and validation.

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%: the single parameter 'dados' is described as a JSON string per the Nuvem Fiscal API. The description adds emphasis on 'complete' data, but this is a minor addition over the schema's own documentation.

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 it emits a new NFS-e, using the specific verb 'Emite' and naming the exact resource. This distinguishes it from sibling tools like 'emitir_nfe', which issues a different type of fiscal document.

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 for emitting NFS-e but does not explicitly contrast with alternatives such as emitir_nfe or provide exclusion criteria. It gives a requirement ('dados completos em formato JSON') but lacks when-to-use guidance.

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