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

The annotations already cover read-only/idempotent behavior, and the description adds valuable behavior beyond them: client-side pagination and a 15-minute cache. These are practical operational caveats that help an agent invoke the tool correctly.

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: purpose, usage signal, pagination, and cache are covered in a few short lines without filler. Every sentence contributes distinct 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?

Given the read-only/idempotent annotations, fully documented parameters, and presence of an output schema, this description is complete enough for safe invocation. The cache and pagination notes cover the main non-obvious calling conventions.

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?

All three parameters are already fully documented in the input schema (100% coverage), so the description is not expected to re-explain them. The pagination note adds some behavioral color but does not need to add schema-level parameter semantics.

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 ("Lista ocorrências/penalidades") and gives the endpoint route, so the tool's purpose is clear. It does not explicitly call out how it differs from related sibling tools such as compras_checar_sancoes_fornecedor, leaving some distinction to inference.

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?

"Indicador-chave da confiabilidade do fornecedor" supplies useful usage context, but it does not say when to use this tool over the related sanctions/supplier tools or state when not to use it. The guidance is adequate but implicit.

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