get_market_holidays

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully states that results are limited to the current year and sorted upcoming-first, but it does not describe output format, update cadence, or explicitly confirm that this is a read-only operation beyond what the tool name suggests.

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 with no filler. It front-loads the most important facts—what the tool returns, the market segment, the time scope, and the sort order—and every word earns its place.

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 zero-parameter, simple list retrieval with no output schema, this description is largely complete: it states the resource, scope, and ordering. The main gap is that the exact return structure/date format is left to inference, but the expected data is self-evident enough for an agent to invoke the tool correctly.

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?

There are zero parameters to document, so the baseline is 4. The description adds a small amount of context by specifying the scope ('current year') and ordering, which clarifies that no user input is needed for this tool's operation.

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 identifies the resource: NSE equity (capital market) trading holidays, with the scope limited to the current year and a defined ordering (upcoming first). It is distinguishable from sibling market-data tools, though it lacks an explicit action verb like 'retrieves' or 'lists'.

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?

No alternatives or when-not-to-use conditions are mentioned, but the description implies usage: when the agent needs NSE trading holiday information. The uniqueness of this zero-parameter tool among siblings makes the intended context reasonably clear, but it does not explicitly route the agent away from other market-data tools.

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