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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds that it reads what the API already collected and never calls the tax authority, which is useful side-effect transparency. The daily-cap phrase is slightly ambiguous but does not contradict the annotations.

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 first sentence is strong and concise, but the later prose about 'manifestation' and 'summary only' is repetitive and confusing. Some sentences could be tightened or removed without losing core meaning.

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?

An output schema exists, so return-value details do not need to be in the description. However, the missing parameter explanation leaves a meaningful operational gap, and the ambiguous remarks about daily caps reduce completeness.

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 schema has two parameters with no descriptions and 0% schema description coverage. The description does not mention limit or offset at all, so the agent gets no guidance on pagination, defaults, or maximum values.

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?

States a specific verb ('List') and a clear object: NF-e documents issued by other companies against this one. It also explicitly contrasts with list_invoices, making the distinction obvious.

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?

Directly names list_invoices as the alternative and explains the difference: that one shows issued documents, this one shows received documents. It also states the tool is read-only and never calls the tax authority, which helps the agent decide when to use it.

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