compras_indicadores_por_periodo

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond that: the 1-hour cache, the focus on API usage rather than procurement data, and the underlying open-data endpoint, which helps the agent anticipate results.

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 first, then endpoint, then the key disambiguation, then use case and cache behavior. Every sentence delivers distinct information with no filler.

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 read-only, paginated query tool with a rich schema and output schema present, the description covers purpose, endpoint, semantics, exclusions, use case, and caching. Nothing needed for correct selection and invocation 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%, with all four parameters already documented in detail, including the month aggregation behavior. The description adds only a high-level 'period (year/month)' hint, which does not materially improve on the schema.

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 states a specific verb and resource: it returns API usage metrics (requests, latency, downloads) by period, not purchasing data. It also names the exact endpoint and explicitly distinguishes itself from the many purchasing-data tools in the sibling list.

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 clear context by saying the tool is useful for temporal analysis of upstream availability and explicitly clarifies it is not for purchasing data. However, it does not name an alternative sibling tool or state a when-not-to-use condition beyond the 'not purchasing data' exclusion.

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