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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the billing tier ('20 credits (Tier 2)') and the algorithmic trait ('equal-split'), which is useful context beyond the annotations, but says nothing about response shape or limits.

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?

One front-loaded sentence plus two bracketed metadata tags, with zero filler. It is efficient, though arguably too terse for a tool in such a dense sibling family.

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?

An output schema exists, so return values need not be described, and annotations cover safety. The description does pin down the dasha level, which is the key discriminator, but it omits how this level relates to its pratyantar/prana/sookshma siblings and what the 'equal-split' computation yields.

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 the schema already documents date/time/latitude/longitude, timezone semantics, houseSystem letters, and the compact-mode fields/precision params. The description names targetDate but adds no format, range, or default information beyond what the schema supplies; 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-resource pairing ('Sthira Antardasha') and defines the level precisely as 'equal-split sub-periods of running MD at targetDate', which tells an agent this is the antardasha layer rather than the mahadasha itself. It does not, however, name any sibling such as astroway_vedic_dashas_sthira_pratyantar or sthira_maha to disambiguate the family.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. Given roughly 45 near-identical dasha siblings (maha/antar/pratyantar/sookshma/prana across nine dasha systems), the absence of any 'use this when you need X instead of Y' instruction is a real gap.

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