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

The annotations already mark this as read-only and idempotent, so the description effectively adds context: it is hosted by the platform, requires no platform credentials, costs prepaid credit per query, exposes public (non-confidential) data, and makes the customer responsible for LGPD compliance. This goes well 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 compact and front-loaded: the first sentence states the core function, and each following sentence adds meaningful operational, legal, or data-related context. No wordy filler or repeated schema information.

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 three optional-looking parameters and no output schema, the description should clarify query formation and expectations, but it does not. It gives good legal/operational context but omits critical usage composition and return/error behavior details.

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?

Input schema shows only three strings (ie, cpf, cnpj) with no descriptions or required fields. The description does not explain these identifiers, their formats, or whether exactly one is required. Coverage is 0%, and the description offers no compensatory guidance for choosing a parameter.

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 immediately identifies the tool as a consultation of SEFAZ SE's official Certidão de Débitos. The verb 'consultar', the resource 'Certidão Negativa de Débitos', and the official source provide clear, specific purpose that distinguishes it from the unrelated sibling 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 context is reasonably clear: this is an official Brazilian source query that uses prepaid credits and involves LGPD responsibility. However, it does not explicitly state when to use this tool over alternatives, nor does it explain when not to use it or whether a specific credential is required.

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