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

The description discloses that the operation is a query (read-only), requires payment via prepaid credit, and is from an official source. It also states that the data is not secret, which goes beyond the annotation hints. This exceeds the annotations' 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?

The description is relatively concise but contains some repetitive phrases about official sources. It is structured in multiple sentences but stays focused on the tool's purpose and conditions.

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 description provides context about the tool's origin, payment model, and legal responsibility, which is sufficient for a high-level understanding. However, it lacks details on the expected output or additional usage specifics.

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 input schema has a single parameter 'nfce' of type string, but the description does not explain what this parameter represents. There is no description of the parameter's meaning, format, or constraints, leaving users without guidance on how to provide input.

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 is for consulting NFC-e (Nota Fiscal de Consumidor Eletrônica) from SEFAZ AM, an official source, and mentions it is a query operation. It provides enough context for a knowledgeable user.

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 usage guidance by indicating that prepaid credit is required, no platform credentials are needed, and it highlights the client's responsibility under LGPD for legitimate purpose. However, it does not specify exact scenarios or prerequisites beyond that.

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