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

The description adds meaningful behavioral context beyond annotations: it discloses payment requirements (prepaid credit), that no platform credentials are needed, that the data is non-confidential and sourced from official Brazilian agencies, and assigns LGPD responsibility to the client. These details complement the read-only, idempotent, non-destructive annotations without contradicting them.

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 single paragraph, ~50 words, and every sentence adds relevant information (purpose, hosting, payment, data nature, LGPD). It is not overly verbose, but it could be slightly more structured by separating core purpose from legal/payment notes. Overall, it is efficient and front-loaded.

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?

With 8 parameters lacking any descriptions, no output schema, and no examples or usage scenarios, the description is incomplete. It mentions the tool queries official NFS-e data but does not explain the login/certificate parameters, date ranges, pagination, or expected results. This is insufficient for an agent to invoke the tool correctly, especially with such a complex parameter set.

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 description coverage is 0%, and the description does not explain any of the 8 parameters (e.g., pagina, login_cpf, data_final, pkcs12_cert). Since the schema provides no descriptions and the tool description omits parameter semantics, the agent has no guidance on how to fill these fields, making the tool nearly unusable without external knowledge.

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's purpose: to query received NFS-e (Notas Recebidas) from the official Federal Revenue source. It specifies the resource (NFS-e), the action (consult), and the authoritative origin, which distinguishes it from unrelated siblings like authenticate or connect.

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 context (official source, not confidential, LGPD responsibility, pay-per-query) but does not explicitly state when to use it versus alternatives or mention any prerequisites or conditions for use. It implies that it is for querying NFS-e received notes but lacks explicit guidance on when not to use it or what inputs are required.

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