holiday_list

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the data content ('NSE trading holidays') but does not describe what the tool returns, whether it covers a specific year, or any other behavioral trait. This is a minimal disclosure that goes little beyond the name.

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 extremely concise—four words—with no wasted text. It is front-loaded and easy to parse. However, it is slightly under-specified, so it doesn't earn a perfect 5.

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?

There is no output schema, so the description should explain what the tool returns or at least hint at the data structure. 'NSE trading holidays' gives the topic but not the shape of the result (e.g., a list of dates, perhaps with names or day-of-week). Given the low complexity, a small amount of additional detail would make it complete.

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, and the schema description coverage is 100%, so there is nothing to explain. Per the rubric, a baseline of 4 is appropriate for a no-parameter tool.

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 states 'NSE trading holidays', which clearly identifies the resource as the list of National Stock Exchange holidays. Although it lacks an explicit verb, the tool name 'holiday_list' supplies the action, and it is distinct enough from sibling tools like 'market_status' or 'trade_info'.

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 the tool is used for checking NSE trading holidays, but it does not explicitly say when to use it, when not to, or mention any alternatives. The usage context is straightforward and self-evident, but no direct guidance is provided.

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