cn402_festival_cn

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

The description discloses the output (festivals with Gregorian dates) but lacks full behavioral details like data freshness, output format, or potential side effects. No annotations are provided, so the description carries the burden.

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 front-loaded with examples but includes extraneous pricing info that is not tool behavior. It could be more concise and structured.

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 covers the tool's purpose and basic output but misses details like output structure, pagination, or data source. For a simple tool, it is adequate but not thorough.

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 only parameter 'year' is fully described in the schema with format and default. The description adds no additional parameter meaning, so baseline score applies.

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 provides all traditional Chinese festivals for a given year with Gregorian dates, listing examples and use cases. However, it does not explicitly differentiate from sibling tools like cn402_festival_today.

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 suggests use cases for cultural events and holiday planning, providing some context. It does not specify when to use this tool versus alternatives, such as cn402_festival_today for today's festivals.

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