bcb_indicadores_atuais

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it clearly describes what data is retrieved, it doesn't mention important behavioral aspects like whether this is a read-only operation, if it requires authentication, rate limits, data freshness guarantees, or error conditions. The description only covers the basic functionality without behavioral context.

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 a single, efficient sentence that communicates the complete purpose without any wasted words. It's front-loaded with the main action and immediately specifies the exact indicators retrieved. Every word earns its place in this concise description.

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 parameterless read operation with no output schema, the description adequately explains what data is retrieved. However, it doesn't provide information about the return format, data structure, or any limitations. Given the lack of annotations and output schema, the description should ideally provide more complete context about the response format and any constraints.

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?

The tool has zero parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist. It focuses instead on what data is retrieved, which is the correct emphasis for a parameterless tool. The baseline for zero parameters is 4.

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 the tool's purpose with a specific verb ('Obtém' - obtains) and lists the exact resources (Selic, IPCA, Dólar PTAX, IBC-Br). It distinguishes itself from siblings by focusing on the most recent values of key economic indicators rather than series metadata, comparison, or historical data operations.

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 implies usage context by specifying 'valores mais recentes' (most recent values), suggesting this tool should be used when current economic indicator values are needed. However, it doesn't explicitly state when to use this versus alternatives like bcb_serie_ultimos or bcb_serie_valores, nor does it provide any exclusion criteria.

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