baixar_pdf_nfe

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action 'Baixa' without adding context about permissions, side effects, or error scenarios. It does not reveal whether the operation is read-only, what happens if the NF-e does not exist, or any prerequisites.

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, concise sentence with no wasted words. It front-loads the action and resource, making it easily scannable.

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, the description is minimal but adequate. However, it lacks details such as the expected return (binary PDF), prerequisites, or error handling, which would be valuable for an agent to invoke it correctly.

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?

The schema description coverage is 100% for the single parameter 'id', providing its meaning ('ID da NF-e na Nuvem Fiscal'). The tool description itself adds no additional parameter semantics, but the baseline of 3 applies due to high schema coverage.

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 uses a specific verb 'Baixa' (downloads) and a specific resource 'PDF do DANFE de uma NF-e', clearly distinguishing it from sibling 'baixar_xml_nfe' which downloads XML. It unambiguously states what the tool does.

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 (download the PDF of an NF-e) but does not explicitly mention when to use this over alternatives like 'baixar_xml_nfe'. No exclusions or alternative guidance is provided, relying on the tool name for differentiation.

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