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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real context beyond them: the Swiss Ephemeris / Lahiri ayanamsa methodology, the 365.25-day year convention that affects date precision, the caveat that results are classical themes not predictions, and the privacy statement that birth data is not stored or logged. Missing is any mention of failure modes (e.g. unresolvable place names), which keeps it at 4.

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?

Purpose is front-loaded in the first clause and the enumeration of returned periods is the substance rather than padding. The opening sentence is long and dense with commas, and the trailing sentences (year convention, disclaimer, privacy) are short and purposeful, so it is efficient but not maximally tight.

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?

There is no output schema, so the description carries the burden of describing the return value — and it does so item by item, including the number of upcoming Antardashas. Combined with the privacy note, the computational convention, and the ready-made example questions, an agent has everything needed to call this correctly for an eight-parameter tool.

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 100%, so every one of the eight parameters (birth_date, birth_time, place, latitude, longitude, timezone, date, lang) is already documented with format and defaults in the schema. The description adds only the broad statement that 'dates use a 365.25-day year' and does not elaborate on parameter interaction or required combinations, so baseline 3 applies.

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 ('Calculates the Vimshottari dasha periods of a birth chart') and then enumerates exactly which periods are produced: Moon's nakshatra, balance of the first Mahadasha, the full Mahadasha sequence, and the Mahadasha/Antardasha/Pratyantardasha running on a date. That output inventory is what separates it from the more general natal_chart and vedic_chart siblings, so an agent can route without opening a 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?

Explicit use context is supplied with two concrete example questions ('which Mahadasha am I in', 'when does my Saturn dasha start'), which is strong positive guidance. It does not name a when-not condition or point at an alternative sibling such as vedic_chart for general chart work, so it stops short of a 5.

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