divine_get_month_tithi_list

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

Annotations already declare this read-only, non-destructive, and idempotent, so the description only needs to add value beyond that. It discloses that the output includes start/end times and paksha, but does not describe pagination, response shape, or any special behavior such as ignoring deprecated day/lan fields.

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 sentences, with the main purpose in the first sentence and return content in the second. No filler or repetition; information is front-loaded and easy to scan.

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 that an output schema exists and annotations cover the safety profile, the description is nearly sufficient for an agent to select the tool. It could be improved by noting that day and lan are deprecated or that the endpoint is strictly month-scoped, but the schema already documents those specifics.

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 description does not explain any of the required parameters (month, year, place, lat, lon, tzone) or their formats. Although the nested schema $defs contain property descriptions, the context signal reports 0% schema description coverage, so the description itself was expected to compensate; it does not.

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 states a specific verb and resource: getting the tithi list for a month, returning each day's tithi with timings and paksha. This clearly differentiates it from sibling tools like divine_get_tithi, though it does not explicitly name the alternative or scoping rule.

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 by the phrase 'for a given month' and the monthly-list naming pattern, but there is no explicit guidance about when to prefer this over divine_get_tithi or other monthly list tools. No exclusions or alternatives are provided.

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