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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description does add one operationally useful fact not in the annotations — the 20-credit Tier 2 cost — but says nothing about auth needs, output volume, or that a target date/time is what anchors the 'running' period.

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?

Three short fragments, no filler, with the level definition front-loaded and metadata (group, cost) clearly separated in brackets. Trimmed near the minimum for a definition that still conveys meaning.

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. However, for a tool whose semantics hinge on 'the running' period, the description omits that targetDate/targetTime (or a defaulted now) selects which Pratyantardasha is being subdivided — a relevant gap for a 200+ sibling Vedic toolset.

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% (birth-data body, fields, precision all documented with detailed constraints), so the schema carries the parameter burden. The description adds no parameter guidance of its own, which is the expected baseline 3 when structured fields already do the work.

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 resource — the Sookshma (4th-level) Dasha computed within the running Pratyantardasha — and names the cascade depth, which is exactly the axis that separates it from vimshottari_maha/antar/pratyantar/prana siblings. It stops short of explicit sibling routing (e.g., 'use pratyantar for level 3'), so it lands at 4 rather than 5.

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?

No statement of when to reach for the 4th level versus the shallower Vimshottari levels, and no prerequisites or input requirements are mentioned. The context of 'within the running Pratyantardasha' implies the tool depends on a prior dasha position, but this is never spelled out.

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