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

Annotations indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it creates a real fiscal document and warns to confirm data. It also notes idempotency via external_id, which compensates for idempotentHint=false. No contradiction.

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 bullet-like structure, covering key points in a few lines. It could be more structured (e.g., separate sections) but is efficient without waste.

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 description mentions return of id and status but lacks details on response structure. The 'bulk support' line is vague. Given no output schema and moderate complexity, additional info on return format and error handling would improve completeness.

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?

With 0% schema description coverage, the description explains nfse (required inner fields), external_id (idempotency), and external_ids (bulk). However, the 'company' parameter is unexplained, and the exact format of nfse string is not detailed. Overall adds significant meaning.

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 verb 'Emite' (issues) and the resource 'NFS-e (nota fiscal de serviço)'. It specifies it creates a real fiscal document, distinguishing it from sibling tools like cancelar, consultar, listar.

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 advises to confirm data before calling, provides idempotency guidance via external_id, and mentions bulk support with external_ids. It implicitly differentiates from siblings by context, but lacks explicit 'when not to use' instructions.

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