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

Beyond the annotations (read-only, idempotent), the description adds transparency about data sourcing (official Brazilian sources), non-confidential nature, and legal compliance (LGPD). This provides a clear picture of what the tool does and its side effects (or lack thereof).

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 concise, covering essential aspects in a few sentences. It is slightly repetitive (e.g., mentions 'oficial' multiple times) but overall well-structured and not overly verbose.

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 sufficient context for a simple query tool: purpose, data source, payment model, and legal considerations. It does not specify output format or error handling, but given the tool's straightforward nature, the provided details are adequate.

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 only parameter 'nfce' is named descriptively but the description does not elaborate on its format or meaning (e.g., access key, QR code). The description adds no additional clarification beyond the parameter name, so the semantic coverage is minimal.

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 data from SEFAZ BA (official source), specifying it is a consultation. It distinguishes itself from the sibling tools by focusing on NFC-e, which is unique among the listed tools.

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 mentions practical usage details such as being hosted by the platform, no credentials needed, pay-per-query with prepaid credits, and that it queries non-confidential official data. It does not explicitly compare to alternatives, but the purpose is distinct enough to infer 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.