Brazilian National Holidays

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

The annotations already convey readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context, such as data source, update frequency, or any side effects. It merely restates the function without providing additional transparency.

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 very short, consisting of one sentence plus an attribution. It is efficient and to the point, but the inclusion of 'BrasilAPI MIT' is unnecessary and does not help the agent. Removing that would make it even more concise.

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 low complexity (single parameter, output schema exists), the description is minimally adequate. However, it lacks nuance about what constitutes a 'national holiday' and does not mention that the data is limited to specific years (though schema enforces it). It is not fully complete but sufficient for a simple lookup.

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?

With 100% schema coverage, the baseline is 3, but the description fails to add any meaningful information beyond the schema. The schema already describes the 'year' parameter with constraints and an example. The description does not clarify the parameter further or provide any usage hints.

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 'All Brazilian national holidays for a given year' clearly states the function: retrieving a specific set of holidays for a specified year. The title 'Brazilian National Holidays' further reinforces the scope. This differentiates it from sibling tools like 'calendar.holidays.by_country' which are more generic.

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 no guidance on when to use this tool versus alternatives. It does not mention that it only covers national holidays (not state or municipal), nor does it advise against using it for other countries. There is no indication of constraints or prerequisites.

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