nfse_pdf

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

With no annotations, the description carries the full burden. It discloses the key behavioral trait that the PDF is saved locally and returns the file path ('Retorna o caminho do arquivo PDF salvo localmente'). It stops short of disclosing error handling, file overwrite behavior, or permission requirements, but the primary side effect is clearly stated.

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, front-loaded sentence starting with the verb 'Baixa'. It provides essential information with no filler or redundancy.

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 simple one-parameter tool with no output schema and no annotations, the description sufficiently explains what it does and what it returns. It could mention that the key must belong to an existing NFSe (obtained via sibling tools), but this is implied by the purpose and not a major gap.

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 description coverage is 100% (the only parameter 'chave' is described as 'Chave identificadora da NFSe'). The description adds no extra meaning beyond restating that the download is 'a partir de sua chave'. Baseline of 3 applies as the schema already documents the parameter.

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 downloads the PDF (DANFSe) of a specific NFSe using its key, with a specific verb ('Baixa') and resource. This distinguishes it from siblings 'nfse_buscar' (search) and 'nfse_detalhes' (details).

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 via the action (download PDF from a given key) but does not explicitly state when to use it versus siblings or any exclusions. There is no guidance like 'use nfse_buscar to find the key first' or 'this is the only tool that returns a local file path.'

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