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 does disclose the computation method (derived from the Moon's nakshatra at birth) and the scope of the timeline with antardashas, and an output schema exists so return shape is covered elsewhere. However, it says nothing about prerequisites, determinism, or that the supplied date/time is the birth moment rather than the current time.

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?

Uses labeled sections (WHEN TO USE / WHAT IT DOES / RETURNS / NEXT) that are front-loaded and scannable. Every line earns its place and no sentence restates the tool name.

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?

The output schema means the RETURNS section is a helpful convenience rather than a necessity, and purpose/usage are adequately covered. The gap is parameter documentation: for an 8-parameter, 0%-coverage schema, the description should at minimum clarify that the date/time inputs are the birth moment and what the geo/timezone defaults mean.

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 and largely does not. Only the oblique phrase 'at birth' hints that year/month/day/hour/minute are the birth moment; latitude, longitude, and timezone_offset (defaulted to Indian coordinates and +5.5) are never explained, leaving the agent to guess whether defaults are appropriate.

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 and resource: 'Calculate the Vimsottari Mahadasha sequence and current period,' and the WHAT IT DOES line adds the computation basis (Moon's nakshatra at birth) and 120-year timeline. It is clear, though it never names the obvious sibling calculate_all_dashas, so the agent must infer the boundary between this and the all-systems tool.

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 trigger: the agent needs the planetary period a person is currently running, plus upcoming periods. It also provides a sequencing hint ('NEXT: Use calculate_birth_chart'). It stops short of explicit when-not conditions or naming calculate_all_dashas as an alternative.

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