get_eclipse_calendar

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

With no annotations, the description discloses key behaviors: max range, Sutak only for visible eclipses, and input flexibility (city or coordinates). It does not mention error handling or empty results, but covers the essential behavioral traits.

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 concise yet informative, front-loading the return structure, then constraints, then arguments. Every sentence adds value without redundancy, making it easy for an agent to parse.

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 complexity of eclipse calendar data and the presence of an output schema, the description provides comprehensive details: return fields, max range, Sutak condition, and input options. It covers all necessary aspects for correct invocation.

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 coverage is 0%, so the description compensates by explaining the format for start_date and end_date, the city parameter, and the alternative latitude/longitude/timezone combination. It adds value by clarifying defaults (Hyderabad) and derived behavior (timezone), though individual lat/lon/timezone are not detailed separately.

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 tool returns solar and lunar eclipses with specific details (kind, subtype, visibility, timings) for a date range and city. It distinguishes itself from sibling tools like get_panchangam_range by focusing exclusively on eclipses and including Sutak timing.

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 when eclipse data with Sutak timing is needed, and specifies a max range of 730 days. It does not explicitly contrast with siblings or state when not to use, but provides clear context for appropriate use.

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