baixar_nfe_distribuicao

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

With no annotations, the description adequately discloses key behaviors: requires local A1 certificate, uses mTLS, never sends certificate, supports incremental and specific queries, and notes that full XML requires prior consultation (Ciencia da Operacao). Password safety is highlighted.

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, well-structured paragraph of five sentences. It front-loads the primary action and requirements, then details search modes. Every sentence provides essential information with no 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?

Given 10 parameters and no annotations, the description covers purpose, requirements, and search modes. It mentions a prerequisite (Ciencia da Operacao) for full XML. An output schema exists, so return values are not needed. It lacks error handling or rate limits but is otherwise complete.

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?

Although schema coverage is 100%, the description adds meaningful context by explaining the search modes (distNSU, consNSU, consChNFe) and their parameters (ultimo_nsu, nsu, chave). It goes beyond schema definitions by clarifying usage semantics like default NSU and prerequisites.

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 NFeDistribuicaoDFe using a local A1 certificate. It lists three search modes (distNSU, consNSU, consChNFe), distinguishing it from sibling tools like consultar_nfe or manifestar_nfe which serve different purposes.

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 downloading fiscal documents and specifies prerequisites (certificate, CNPJ, UF). However, it does not explicitly state when to use this tool versus alternatives or provide when-not-to-use guidance, leaving agents to infer from context.

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