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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful operational context the annotations do not carry — the endpoint and the 20-credit (Tier 2) cost — but says nothing about the shape or volume of the 5-level cascade output.

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?

Extremely compact: one content sentence plus bracketed metadata for group, endpoint and cost. Front-loaded and free of filler, though the single content sentence is arguably too terse for the domain it describes.

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 explained, and the nested input schema is richly documented. What is missing is the domain context an agent needs to pick this tool over its many siblings: what distinguishes prana from sookshma, and what the cascade actually returns.

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 body/fields/precision are already documented in detail (including timezone, ayanamsa and houseSystem caveats). The description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description identifies the specific resource (Yogini Pranadasha, the deepest level of the Yogini dasha cycle) via the name and '5-level cascade (finest grain)'. However, 'finest grain' is jargon that only helps an agent who already knows the maha > antar > pratyantar > sookshma > prana hierarchy; it does not explicitly distinguish this from astroway_vedic_dashas_yogini_sookshma or the other 60+ dasha siblings.

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 at all: no statement of what a prana-level dasha is for versus the coarser sookshma/pratyantar levels, no prerequisites, and no alternatives named despite a very dense sibling set of dasha tools.

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