Feriados Bancários (FEBRABAN)

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

With no annotations, the description adequately describes what the tool returns (list of bank holidays, including facultative ones) and filtering capabilities. However, it does not disclose all behavioral traits such as default behavior when no parameters are provided, or response format, which are missing.

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 informative paragraph that covers key aspects without redundancy. It could be slightly more structured (e.g., bullet points) but effectively communicates the tool's purpose and options in a compact form.

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 parameter count, full schema coverage, and no output schema, the description provides sufficient context for understanding the tool. It explains the special holidays, filtering, and intended use, though some details like default year or response format are absent.

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 baseline is 3. The description adds value by explaining the context of each parameter (e.g., UF for state holidays, facultativos for voluntary days) and linking to the FEBRABAN standard, which enriches understanding beyond schema metadata.

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 bank holidays from the official FEBRABAN calendar, including specific facultative dates. It clearly distinguishes from siblings like 'feriados_nacionais' by focusing on banking holidays, making the purpose unmistakable.

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 context on ideal use cases (e.g., calculations for due dates, compensations) and mentions filtering options. While it does not explicitly state when not to use or list alternatives, the context and sibling names imply the distinction from general holiday tools.

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