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

The description adds meaningful behavioral context beyond annotations: it states no platform credentials are needed, queries are prepaid, data is non-confidential, and the client is responsible for LGPD compliance. This enriches the readOnly/idempotent/destructive hints already provided by annotations without contradiction.

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 four-sentence paragraph that includes both core purpose and legal/payment disclaimers. While not excessively long, the LGPD and payment details could be condensed without losing essential information. It is reasonably structured but less crisp than the high-scoring two-sentence examples.

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?

For a simple query tool with one parameter, no output schema, and comprehensive annotations, the description covers key aspects: official source, payment model, privacy obligations, and non-confidential nature. It lacks explicit return-value details, but this is mitigatable given the query nature and no output schema requirement.

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?

With a single required parameter 'nfce' and zero schema description coverage, the description should compensate. It implies the parameter is the NFC-e identifier (from the tool name and context) but does not explicitly define its format, validation, or expected values. This adds some meaning but leaves room for ambiguity.

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 queries NFC-e (Nota Fiscal de Consumidor Eletrônica) from the official SEFAZ GO source. It uses specific verbs ('consulta') and identifies the resource, distinguishing it from sibling tools that handle platform management (auth, marketplace, etc.).

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 explicit guidance on when to use this tool versus alternatives. It mentions hosting and payment details but does not indicate prerequisites, exclusions, or situations where another tool should be preferred. The sibling tools are not referenced, and no alternative use cases are described.

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