get_lunar_festivals

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

No annotations are provided, so the description carries the full burden. It states that the tool returns festival names, significance, customs, and cultural importance, but does not disclose any limitations (e.g., supported cultures beyond Chinese, date range constraints, or whether the list is exhaustive). This leaves ambiguity about behavior for non-Chinese cultures.

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?

Two focused sentences: the first defines the primary function, the second provides illustrative examples. No redundant or filler content. Information is front-loaded.

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 no output schema, the description partially explains return content (names, significance, customs, cultural importance), but omits structural details, error handling, or completeness guarantees. For a tool with multiple siblings, this is adequate but not thoroughly 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?

Schema coverage is 100% with both parameters described. The description adds context for the 'culture' parameter by associating it with Chinese traditions, but does not provide additional technical details beyond the schema. Baseline of 3 is appropriate.

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 verb 'retrieves' and the resource 'traditional festivals and cultural celebrations' for a specific date. It provides examples like Spring Festival, Mid-Autumn Festival, which distinguish it from sibling tools like get_annual_festivals (lists all festivals across year) and get_festival_details (for a single festival).

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 usage for a specific date and Chinese culture via examples and default parameter, but does not explicitly state when to use this tool over siblings like get_festival_details or get_annual_festivals. No exclusions or alternative tools are mentioned.

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