baixar_nfe_distribuicao

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

In the absence of annotations, the description carries full responsibility for behavioral disclosure. It states that the certificate is never sent to any server, authentication is local via mTLS, and the password is never logged or included in exceptions. It also notes the prerequisite for obtaining complete XML, providing important behavioral context.

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 and well-structured, using a few sentences to cover the main functionality, requirements, security aspects, and modes. It avoids redundancy and stays focused on essential information.

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 provides sufficient context for an agent to decide when to use the tool and how to configure it, including modes, credentials, and prerequisites. However, it does not describe the output format or return value, which would complete the picture for the agent.

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 already provides detailed descriptions for all 10 parameters (100% coverage), so the baseline is 3. The description adds some context about the certificate and the event prerequisite, but it does not significantly expand on each parameter's meaning beyond what the schema already specifies.

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 fiscal documents via the NFeDistribuicaoDFe SEFAZ service, specifying the verb 'Baixa' and the resource 'documentos fiscais'. It differentiates by mentioning the local certificate requirement and the three supported modes, making its purpose unambiguous.

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 explains the three operational modes (distNSU, consNSU, consChNFe) and notes the prerequisite of the 'Ciencia da Operacao' event, but it does not explicitly contrast this tool with sibling tools like consultar_nfe or validar_chave_nfe. Thus, when-to-use vs alternatives is implied rather than explicit.

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