obter_metadados_agregado

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

No annotations, but the description makes it clear the tool is read-only and returns metadata. It could mention response size or limits, but the presence of an output schema reduces the need. Solid for a straightforward retrieval.

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?

Two sentences, no wasted words. Front-loaded with the main purpose, then immediate usage guidance. Highly 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?

Complete for a simple metadata tool. Covers what it does and how to use the result. With an output schema, no further details needed.

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?

Only one parameter with 100% schema coverage. The description adds an example value (6579) which helps contextualize the parameter beyond 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 clearly states it retrieves metadata of an aggregate from SIDRA, specifying exactly what kind (variables, periods, territorial levels). It distinguishes from sibling tools that list or query data.

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?

Explicitly advises to use the result to choose parameters for 'consultar_dados_agregado', providing clear usage context. No explicit when-not, but the guidance is strong.

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