compras_aggregate_contratacoes_por_periodo

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

The description clearly explains the behavioral differences between count mode (fast, one call) and valor_* mode (pagination, slower, truncation). It even names the internal concurrency (4 calls) and cache duration (30 min). Since no annotations were provided, the description properly carries this burden.

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 well-structured with clear sections, uses bold for emphasis, and each sentence serves a purpose. It could be slightly more concise by removing the 'Concurrency interna' line which is an implementation detail, but is otherwise efficient.

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 tool's moderate complexity (7 parameters, 2 modes, pagination) and the presence of an output schema, the description covers key behaviors, modes, limits, and constraints. It does not explain the return value format for count mode versus valor_* mode, but the output schema presumably handles that.

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 description primarily adds context for the metrica and granularidade parameters (recommending count for trends, explaining bucket sizes). The overall parameter documentation is already complete in the schema, so the description provides marginal but useful nuance.

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 this tool produces a time series of hiring data (contratações) aggregated by time buckets. However, it does not explicitly differentiate itself from the many sibling tools that also query contracting data, such as compras_contratacoes_14133_listar or compras_indicadores_consolidados, which may have overlapping purposes.

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 provides direct guidance on when to use count vs valor_* modes, including performance implications and page limits. It does not, however, explicitly state when to prefer this tool over siblings like compras_indicadores_por_periodo or compras_contratacoes_14133_listar for time-series queries.

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