bcb_buscar_serie

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

Annotations already declare readOnlyHint and idempotentHint. Description adds that it searches a local catalog without network calls, and explains accent/case insensitivity and empty result behavior.

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?

Description is well-structured with when to use, when not, limitations, and return format. It is informative but slightly dense; each 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?

Given low complexity (1 parameter, output schema present), the description fully covers purpose, usage, behavior, and return structure, including the array of series objects and empty result handling.

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 only provides minLength and a basic description. The tool description adds that the search is by name or category, ignores accents and case, and gives examples like 'inflacao' finds 'Inflação'.

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 searches series in an internal curated catalog by name or category, with accent and case insensitivity. It distinguishes from sibling tools like bcb_series_populares.

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?

Explicit when to use (to find series code from keyword) and when not to use (for listing by category, use bcb_series_populares). Also mentions limitation to curated catalog only.

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