gerar_danfe

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

With no annotations, the description discloses key behaviors: it generates a PDF, returns it in base64, requires a specific namespace, and does not need a digital certificate. It could mention potential errors or limits, but it's adequate.

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, front-loaded with the main action, and every sentence adds value (specifies model, output format, important warning). No wasted words.

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 single-parameter tool with an output schema that likely describes the base64 PDF, the description covers all necessary context. An agent can confidently use this tool based on the provided information.

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 single parameter 'xml_content' has 100% schema coverage, so baseline is 3. The description adds minor context (namespace requirement, wrapper acceptance) that is already present in the schema description. No significant additional meaning beyond the schema.

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 it generates a DANFE PDF from an NF-e XML, specifying the model (55) and output format (base64). This distinguishes it from sibling tools like parse_nfe_xml or consultar_nfe.

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 provides clear context for when to use this tool (for NF-e model 55, no digital certificate needed) but does not explicitly mention when not to use it or compare it to alternatives. The warning about namespace is helpful.

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