get_combustion_calendar

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

With no annotations, the description describes the operation's behavior: returns periods, explains accuracy, max range, and parameter fallbacks. Discloses that it is a read operation matching Drik Panchang. No contradictions.

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?

Single paragraph with multiple pieces of information, well-structured and front-loaded. Could be slightly more concise, but every sentence provides value.

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 presence of an output schema, the description covers purpose, parameters, accuracy, and constraints. Does not detail the return structure, but the output schema fills that gap.

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 has 0% description coverage, so the description fully compensates: explains date format, city handling, optional planets list, and latitude/longitude/timezone fallback. Adds significant value beyond the raw 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 it returns Asta and Udaya periods for five classical planets over a date range. It defines the terms and distinguishes this tool from other astronomical tools like get_graha_positions or get_eclipse_calendar.

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?

Provides context on when to use: for heliacal setting/rising periods, with accuracy and max date range. Distinguishes from BPHS thresholds but does not explicitly name alternative tools or state when not to use.

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