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

Annotations already declare the tool as read-only and non-destructive. The description adds useful operational details: it's hosted by the platform, requires prepaid credits per query, needs no platform credentials, and involves LGPD responsibilities. This goes beyond the annotations and clarifies the tool's external dependencies and compliance context, which is valuable for an agent.

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, one sentence with additional clauses, and front-loads the core purpose. However, it could be slightly more structured, but it avoids unnecessary verbosity.

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 the simplicity of the tool (no output schema, only three obvious parameters), the description provides adequate context about payment, hosting, and data source, but it lacks any detail about parameter usage or expected results, making it moderately complete.

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 input schema has zero descriptions for the three parameters (ie, cpf, cnpj), and the description does not mention or explain these parameters at all. No guidance is provided on what values to provide or how they relate to the query, leaving the agent without sufficient information to construct a valid request.

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 it consults negative debt certificates from SEFAZ RO, specifying the resource and action. It mentions official sources shines light on its purpose. It distinguishes by specifying the state (RO) and type of certificate, which is unique among the 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 description mentions payment with prepaid credits and no platform credentials, but it does not explain when to use this tool versus alternatives, nor does it provide any selection criteria. There is no explicit guidance on when this tool should be invoked or when another might be better.

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