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

Annotations already declare read-only, idempotent, non-destructive behavior. The description usefully adds that the query costs prepaid credits, requires no platform credentials, processes non-confidential official data, and involves LGPD obligations. This goes beyond the annotations and helps the agent understand cost, legal, and data governance traits.

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 compact and front-loads the main purpose, then briefly covers operational, cost, confidentiality, and legal points. It could be slightly more concise by merging the LGPD and business terms, but overall the length is reasonable and every sentence contributes meaningful context.

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 with four self-describing parameter names, the description provides good contextual detail about cost, hosting, and legal aspects. However, because there is no output schema, it doesn't describe the return structure or content, nor does it clarify at least one identifier (CPF/CNPJ) must be provided, leaving some ambiguity for the agent.

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 has 0% description coverage, and the description does not explain the four parameters (cpf, cnpj, nome_contribuinte, preferencia_emissao). While the property names are fairly self-explanatory for a Brazilian audience, the description adds no clarification about formats, required combinations, or constraints, so it fails to fill the schema documentation gap.

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 specifies the exact resource and action: 'SEFAZ SC: Certidão Negativa de Débitos, consulta em fonte oficial.' This clearly identifies it as a query tool for a specific Brazilian official tax debt certificate and distinguishes it from the platform-level sibling tools (authenticate, connect, marketplace, etc.).

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 useful context: it is an official-source query, hosted by the platform, requires no platform credentials, and consumes prepaid credits. However, it does not explicitly state when to use this tool versus alternatives or what preconditions apply (e.g., which identifier must be provided), though no sibling tool appears to be a direct alternative.

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