br__generate_nfse

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

No annotations provided, so description carries full burden. It discloses that the output lacks ds:Signature, describes the return value structure (xml, dps_id, warnings), and mentions the schema version. It does not mention authentication or side effects, but the tool is read-only generation, so no major gaps.

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 very concise: one line for purpose, followed by essential details on unsigned signature and return values. Every sentence provides value without 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 one parameter, an output schema (implied), and sibling tools, the description covers the workflow and return values. Could provide more detail on the dps nested object structure, but it's sufficient for an experienced user.

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%, with the dps parameter described as 'DPS data matching the NFSeDocument schema'. The description adds only that it is for NFS-e Nacional and schema v1.01, which is already in the schema description. Minimal additional meaning beyond 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 an unsigned DPS for NFS-e Nacional, schema v1.01. It distinguishes from siblings br__sign_nfse and br__submit_nfse by specifying the unsigned nature and the subsequent workflow.

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?

It explicitly instructs to sign the DPS with br__sign_nfse before submitting via br__submit_nfse, providing a clear workflow. However, it does not explicitly state when not to use this tool or mention alternatives beyond the implied workflow.

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