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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by disclosing that the platform hosts the service, requires prepaid credit per query, and that the client is the data controller under LGPD. This goes beyond the annotations to explain operational and legal aspects, though it doesn't detail rate limits or exact response format.

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, reasonably concise paragraph that front-loads the purpose. It covers multiple aspects (purpose, hosting, payment, legal) without excessive verbosity. However, it could benefit from structured bullet points for clarity, but as is, it's adequately concise.

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?

Given there is no output schema, the description should clarify what the tool returns (e.g., certificate status, document). It does not specify the output format or the expected response. Additionally, the lack of parameter semantics further reduces completeness, making it difficult for an agent to invoke it correctly. The legal and usage context is helpful but not sufficient for correct invocation.

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 three parameters (ie, cpf, cnpj) with zero description coverage, and the description fails to explain their meaning or usage. It does not say which identifiers can be used or whether they are mutually exclusive. This is a critical gap since the agent must know how to construct the query.

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 identifies the tool as a consultation for a negative debt certificate (Certidão Negativa de Débitos) from SEFAZ RN, a specific official source. The verb 'consultar' (query) and resource are unambiguous, making it distinct from sibling tools which are unrelated (authenticate, connect, 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 context about the data being public and from official sources, and mentions payment via prepaid credit. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The guidance is implicit rather than explicit.

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