get_panchangam_range

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

With no annotations, the description carries full burden. It discloses the max range (31 days), detailed return fields (including new in 1.9.0), and all arguments. It lacks mention of error handling or rate limits, but the depth of content listed makes it fairly transparent.

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 well-structured: purpose first, then content, new features, use case, and arguments. It is somewhat long but each sentence adds value, and there is no unnecessary 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?

Given the tool's complexity (range of dates, many fields) and the existence of an output schema, the description is thorough about return content and inputs. It covers the max range and new fields but could mention error or truncation behavior for exceeding 31 days.

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 0%, so the description adds significant value by listing start_date, end_date, city, system, and ayanamsa with defaults. However, it omits latitude, longitude, and timezone, which are present in the schema. Thus, it partially compensates but is incomplete for all 8 parameters.

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 it returns a compact Panchangam summary for each day in a date range (max 31 days), listing all included elements. This distinguishes it from the sibling tool get_panchangam (single day) by emphasizing the range scope and specific content.

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 suggests usage for 'planning muhurtas over a week or comparing multiple days,' providing clear context. However, it does not explicitly state when not to use it or name the alternative (get_panchangam) for single-day queries, though it is implied.

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