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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds transparency by noting that the data is not confidential, is sourced from official channels, and that the client is responsible for LGPD compliance, which provides additional context beyond 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 description is concise, consisting of a few short sentences. It includes relevant operational and legal information without excessive verbosity, though the legal LGPD note adds a bit of extra text that could be streamlined.

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 does not explain what the tool returns or what the output format is. It only states that it 'consults information' without specifying the nature of the result, leaving the agent without a clear expectation of the tool's outcome.

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 provides no descriptions for the parameters, and the description does not explain any of them. It mentions 'without platform credentials' and prepaid credit, but the roles of login_cpf, login_senha, pkcs12_cert, and pkcs12_pass remain entirely unclear, offering minimal compensation for the lack of schema details.

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 that this tool performs a consultation of NFC-e (Nota Fiscal de Consumidor Eletrônica) from official Brazilian sources (SEFAZ). It distinguishes itself from sibling tools like authenticate or connect by specifying its exact function.

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 implies usage for querying official tax-related information and mentions the prepaid credit model, but it does not explicitly state when to choose this tool over alternatives or provide conditions for its use.

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