divine_find_festival

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful context about location-adjusted timing and that it returns one or multiple dates, but it does not disclose error behavior or caveats beyond that. This is adequate but not rich.

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 tightly worded sentences with no filler. The main purpose is front-loaded and the result description follows immediately. Every clause 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?

With an output schema present, the description does not need to explain return fields. It covers the key inputs (festival, year, location) and the location-adjusted aspect. It might optionally mention that festival names must come from the API's predefined list, but that is already fully covered in the festival parameter's schema description.

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%, and the festival parameter already includes detailed semantics including the allowed value format and rejection behavior. The description's mention of 'given year' and 'location-adjusted timing' aligns with the parameters but adds no new meaning 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 a specific verb ('Find') and resource ('date(s) of a specific festival in a given year'), and even adds return details. It does not explicitly differentiate from sibling tools like divine_get_festivals_by_date, but the phrase 'specific festival' makes the core purpose unambiguous.

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: use this tool when you need the date(s) of a named festival for a specific year and location. However, it provides no explicit guidance about when not to use it or which sibling tool to prefer (e.g., when you need festivals by date instead).

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