compras_indicadores_consolidados

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds useful behavioral details beyond annotations: the endpoint path, the 1-hour cache, and the scope limitation to operational metrics rather than market indicators.

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?

Three concise sentences with no filler. The purpose and endpoint are front-loaded, followed by return fields, usage guidance, and cache behavior. Every sentence earns its place.

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?

For a simple read-only metrics tool with an output schema, the description is complete: it specifies the endpoint, the returned metrics, the intended use case, an explicit exclusions, and cache behavior. Nothing needed to select and invoke it correctly is missing.

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%, and both parameters (página, tamanho_pagina) already have clear descriptions in the schema. The tool description does not need to add parameter detail, so baseline 3 applies.

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 identifies a clear, specific resource: consolidated operational metrics of the Dados Abertos API, and lists the exact endpoint and metrics returned. It distinguishes itself from sibling tools by explicitly stating it is not for public market indicators, helping an agent tell it apart from related indicator 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?

It explicitly states when to use this tool: for diagnostics and observability, and when not to use it: not for public market indicators. This gives clear selection guidance even without naming a specific sibling alternative.

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