bcb_series_populares

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

Annotations already indicate read-only, non-destructive, and idempotent traits. The description adds that the tool uses a local catalog (no network call) and details the return structure, enhancing transparency beyond the annotations.

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 a clear opening, usage sections, return format, and a note about the local catalog. Every sentence adds value, and there is no redundancy.

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, the description covers purpose, usage, return format, and local nature. An output schema formally defines return values, so the description is complete for contextual understanding.

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% with parameter description listing categories. The description adds context by explaining the effect of the filter on output structure (grouped vs flat array), which goes beyond the schema's basic description.

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 explicitly states the tool lists a curated catalog of 150+ economic series, grouped by category, and distinguishes it from siblings like 'bcb_buscar_serie' which is for keyword search. It clearly specifies the verb 'Lista' and the resource 'catálogo interno curado'.

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 explicit 'Quando usar' (when to use) and 'Quando NÃO usar' (when not to use) guidance, including a direct alternative (use bcb_buscar_serie for keyword search). This helps the agent make clear decisions.

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