listar_nfse

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

No annotations are provided, so the description bears the responsibility for behavioral disclosure. The verb 'Lista' implies a read-only operation, but the description does not disclose whether canceled invoices are included, result ordering, pagination behavior (beyond schema), or response format. It adds limited context beyond the action itself.

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, focused sentence with no extraneous words. It conveys the essential purpose efficiently and earns its place.

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?

This is a simple list tool with a small schema, but no output schema or annotations exist. The description defines the core functionality and filter, but omits details about the returned payload, status filtering, or how to handle pagination in practice. It is adequate for a basic list tool but leaves room for more context.

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%: all three parameters (cpf_cnpj, top, skip) have clear descriptions. The tool description adds no additional parameter information beyond what the schema already provides, so the baseline of 3 applies.

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's function: 'Lista as NFS-e emitidas por um CNPJ/CPF' (Lists the NFS-e issued by a CNPJ/CPF). It uses a specific verb 'Lista' and identifies the resource (NFS-e) and scope (by CNPJ/CPF), distinguishing it from siblings like 'listar_nfe' (which lists NFe) and 'consultar_nfse' (which likely retrieves a single invoice).

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: use this when you need to list NFS-e for a given CNPJ/CPF. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or comparisons to sibling tools such as 'consultar_nfse' or 'listar_nfe'.

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