Kasra Get Holidays

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

With no annotations, the description carries the full burden. It discloses that it returns holidays for the year, which is a scope detail. However, it does not explicitly mention that the operation is read-only, nor does it address any potential side effects, authentication, or rate limits. The behavior is implied by the 'get' verb but not explicitly stated.

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 concise, using two sentences (Persian and English) to state the purpose. It is front-loaded and contains no unnecessary fluff.

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?

The description provides the core purpose but omits explanation of the 'reason' parameter and any context about how the year is determined. Given that an output schema exists, return format is covered, but the parameter and any usage constraints are missing.

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 schema has one optional parameter 'reason' with no description (0% coverage). The description does not mention this parameter at all, leaving its purpose and expected format entirely undefined. The agent has no information about what to pass for 'reason'.

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 that this tool retrieves official calendar holidays for the year. It uses a specific verb (get) and resource (holidays), and is distinct from sibling tools like kasra_get_profile or kasra_get_daily_report which serve different purposes.

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 explicit guidance on when to use this tool over alternatives. It only states what it does, implying usage when holiday data is needed, but does not mention any exclusions or alternative tools.

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