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

The annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful context beyond that: the 1-hour cache TTL and the operational significance of active sanctions. This is genuinely additive and not redundant.

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 compact set of three short paragraphs with no filler. It front-loads identity and endpoint, then gives business relevance, usage guidance, and cache TTL in only a few sentences.

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 a full input schema, an output schema, and complete safety annotations, the description is nearly complete. The main gap is that it does not clarify that CEIS is only one of several sanction registries and that a comprehensive compliance check might require sibling tools.

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?

Schema description coverage is 100%, so the schema already documents all four parameters, including CNPJ, name, page, and sanctioning body. The description does not add parameter-level details, but the baseline 3 is appropriate since the schema carries the burden.

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 opens with a specific verb and resource ('Consulta CEIS — Cadastro de Empresas Inidôneas e Suspensas') and identifies the exact endpoint. This makes the CEIS registry unmistakable relative to sibling sanction tools such as CNEP, CEAF, and CEPIM.

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?

It gives an explicit trigger: 'Use sempre antes de homologar pregões e contratos.' It does not name sibling tools like compras_sancao_cnep or compras_checar_sancoes_fornecedor for cases where CEIS alone may be insufficient.

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