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

No annotations are provided, so the description carries the full burden; it discloses that this is a computation scoped to a supplied location and timezone offset and details the returned data (muhurat windows, choghadiya divisions). It stops short of noting behavioral caveats such as the effect of ayanamsa_mode or the 0,0 latitude/longitude defaults, keeping it from a 5.

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 labeled sections (WHEN TO USE / WHAT IT DOES / RETURNS / NEXT) are front-loaded and scannable, with no filler. The RETURNS section is somewhat redundant given the output schema exists, costing a point on pure economy.

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?

Purpose and return content are well covered (and the output schema handles structured returns), but for an 8-parameter tool with zero schema description coverage the semantics of the inputs are left to inference. Adequate at the top level but incomplete on parameters.

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% across 8 parameters, so the description must compensate but largely does not. It only gestures at 'supplied location and timezone offset,' leaving year/month/day, hour, and especially ayanamsa_mode entirely unexplained.

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?

States a specific verb (Calculate) and resource (Panchanga/Vedic calendar factors) and enumerates the exact factors produced (tithi, nakshatra, yoga, karana, weekday). It also differentiates from a sibling by directing person-specific work to calculate_birth_chart, so an agent can distinguish it without opening the schema.

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 'WHEN TO USE' line gives a concrete context (planning or interpreting a date) and the 'NEXT' line names the alternative (calculate_birth_chart) for person-specific interpretation. It lacks explicit when-not/exclusion conditions, but the routing guidance is clear.

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