divine_get_english_calendar_festivals

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds that it returns all festivals falling within the month, but does not disclose why location/timezone parameters are needed or any edge cases in date computation.

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 two tight sentences with no filler. The primary scope ('English calendar month') is front-loaded, and the second sentence reinforces the return semantics without repetition.

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?

Output schema and annotations cover much of the operational context, but the description omits why six required parameters including lat, lon, place, and tzone are needed for a festival lookup. It also does not help an agent distinguish this tool from similar festival-related siblings.

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%, with each parameter having type and example documentation. The description itself adds little beyond noting the Gregorian-month scope, so the baseline of 3 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 action and resource: 'Get all Hindu festivals for a specific English calendar month' and clarifies the calendar system as Gregorian. However, it does not explicitly distinguish itself from sibling festival tools such as divine_get_festivals_by_month or divine_get_festivals_by_date.

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 usage context is implied: use when seeking Hindu festivals within a Gregorian month. No alternatives or exclusions are given, and the description does not explain when to choose this over the many other festival-related sibling tools.

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