Verificar Dia Útil Bancário

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

Without annotations, the description discloses return behavior (reason and next business day) and the calendar source (FEBRABAN with specific holidays). It could mention side effects or idempotency, but the core behavior is clear.

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 three sentences, front-loaded with purpose, then usage examples, then behavioral details. No redundant language.

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 single-parameter tool with no output schema and no annotations, the description covers purpose, usage, behavioral details, and calendar specifics. It is complete for an agent to decide when and how to use it.

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 does not add extra semantics beyond the schema's format and example for the 'data' parameter.

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 checks if a date is a bank business day, with a specific verb 'verifica' and resource 'dia útil bancário'. It distinguishes from siblings like 'verificar_data' (generic) and 'feriados_bancarios' (holiday list) by focusing on business day status.

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 example queries ('o banco abre amanhã?') and implies when to use. It also indicates what the tool does if the date is not a business day, offering guidance on behavior and alternatives.

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