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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: data is of public access, not private/confidential, and the client is data controller under LGPD. This goes beyond annotations and helps an agent understand the sensitivity and legal framing.

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 and front-loaded with the core function. It includes necessary context about hosting, payment, and legal aspects. While the LGPD clause adds length, it is relevant and does not feel wasteful. Overall efficient.

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 read-only query tool, the description covers purpose, access mode, payment, data sensitivity, and legal responsibility. It does not describe the return format, and the 'completo' parameter remains ambiguous, but overall the context is sufficient for an agent to understand the tool's capabilities.

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?

Schema coverage is 0%, so the description must compensate. It mentions CNPJ and ano ('a partir do CNPJ e do ano'), which clarifies the purpose of those required parameters. However, the optional parameter 'completo' is not explained, and no format/validation guidance is provided. Description partially compensates but misses the optional param.

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 'Consulta as inutilizações de numeração de Nota Fiscal Eletrônica' which is a specific action on a specific resource. It distinguishes from sibling tools which are generic (authenticate, connect, marketplace) and unrelated.

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 clear context: 'Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago' and indicates public access data. This tells when to use it (pay-per-query, no auth) but does not explicitly exclude alternatives or state when not to use.

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