nfse_detalhes

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

With no annotations provided, the description must disclose side effects and context. It reveals a significant side effect: 'salva o XML localmente' (saves the XML locally). It also lists return data. However, it lacks deeper context such as authorization requirements, failure modes, or the format/path of the saved XML. Thus, it provides basic but not exhaustive transparency.

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?

Two short sentences that are entirely informative: first states the main purpose, second lists return data and the side effect. No filler or repetition.

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 tool is simple with one parameter and no output schema. The description covers the main function, the specific return elements, and the local XML saving side effect. It lacks only minor details (e.g., where the XML is saved, whether it returns anything beyond a confirmation), but overall it is sufficiently complete for invocation.

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%, as the 'chave' parameter already has a description ('Chave identificadora da NFSe'). The tool description redundantly mentions 'a partir de sua chave' but adds no new semantic detail about the key's format or constraints. Baseline 3 is appropriate.

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 the specific verb 'Obtém' (gets) with the resource 'detalhes completos de uma NFSe específica' and specifies the input source 'a partir de sua chave'. It also lists the returned data categories (cabeçalho, emitente, valores, DPS), clearly distinguishing it from sibling tools like nfse_buscar (search) and nfse_pdf (PDF generation).

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 clearly indicates when to use the tool: when you have a specific NFSe key and need complete details. It provides context without explicitly naming alternatives or exclusions, but the sibling tools imply differentiation. Given the clear context, it earns a 4.

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