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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that the tool supports filters (date range, status, pagination) but does not disclose how pagination works, default page sizes, ordering, or limits. No additional behavioral traits beyond annotations are revealed.

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 sentence that efficiently conveys the tool's purpose and available filters. It is front-loaded and to the point. However, the omission of the 'account' parameter is a minor flaw, but overall conciseness is strong.

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 the absence of an output schema, the description should explain the return structure or pagination behavior. It does not. It also fails to mention that the tool returns a paginated list, what the default page size is, or how to handle the 'account' parameter. The description is incomplete for effective usage.

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 0%, so the description must compensate. It lists 5 of the 6 parameters (missing 'account') and provides minimal semantics by naming the filters (e.g., 'tamanho_pagina' as page size). However, it does not specify data formats for dates, possible values for status, or the meaning of 'account'. The omission of one parameter reduces completeness.

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 lists issued fiscal notes (NF-e), which is a specific resource type. It implicitly distinguishes from siblings like 'contaazul_get_invoice_nfe' and 'contaazul_list_invoices_nfse' by using the term 'NF-e', but does not explicitly differentiate. The verb 'Lista' (lists) is precise.

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 no guidance on when to use this tool versus alternatives. It does not mention that 'contaazul_get_invoice_nfe' is for a single invoice or that 'contaazul_list_invoices_nfse' lists a different type. The context of usage is only implied by the tool name and filter list.

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