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

The description adds valuable behavioral details beyond the readOnlyHint/idempotentHint annotations: it notes the client-side esfera filter behavior, that _total_registros still reflects the unfiltered total, and that responses are cached for 15 minutes. This helps agents understand side effects and data semantics.

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: three short, informative sentences with the core purpose and endpoint first, followed by the monitoring use case, filter caveat, and cache behavior. No waste.

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 high schema coverage, presence of an output schema, and strong annotations, the description adds exactly the missing context: why to use this tool, the client-side filtering nuance, the cache, and the endpoint. The agent has enough to select and invoke it correctly.

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 coverage is 100%, so the schema already documents every parameter thoroughly. The description mostly repeats the client-side esfera behavior found in the schema, adding no substantially new parameter guidance. Baseline 3 is appropriate.

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 the tool's function with a specific verb and resource: lists contracts changed in a period (PNCP), and immediately clarifies the use case of discovering notices that underwent retifications/republications. It distinguishes itself from sibling tools like compras_pncp_contratacoes_publicacao and compras_buscar_contratacoes_similares by focusing on updates over time.

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 gives clear context for when to use the tool: for monitoring changes and retifications to public notices. It does not explicitly name alternative tools or state when not to use it, but the monitoring use case is specific enough to guide tool selection.

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