get_next_festival

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 discloses the return fields (name, date, days remaining, significance) and the input date reference, but does not mention any side effects, authorization needs, or limitations (e.g., supported cultures beyond Chinese). The description is adequate but not comprehensive.

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?

Three sentences, front-loaded with the main action and purpose. The second and third sentences add context and output details. No wasted words, though the second sentence ('Useful for planning...') is slightly redundant given the first.

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 the tool's simplicity (2 parameters, no output schema), the description explains what is returned (name, date, days remaining, significance). This is sufficient for an AI agent to understand the output. However, it lacks details like date format or if the result is singular. Still, it is reasonably 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 description coverage is 100%: both 'date' and 'culture' have descriptions. The description adds context that the festival is found 'after a given reference date' and is 'traditional,' but does not elaborate on the 'culture' parameter (e.g., valid values). Thus, it adds minimal value beyond the schema.

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 'Finds' and the specific resource 'next upcoming traditional festival after a given reference date.' It distinguishes itself from siblings like 'get_annual_festivals' and 'get_festival_details' by focusing on the immediate next festival, not a list or details of a known 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 mentions 'useful for planning ahead,' implying a temporal context, but does not explicitly specify when to use this tool versus alternatives (e.g., 'get_festival_details' for detailed info on a known festival, or 'get_annual_festivals' for a yearly list). No when-not-to-use guidance.

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