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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral context beyond them — the recursion preserves the natal chakra-row and paramayu, and the call costs 20 credits (Tier 2) — but says nothing about how many periods are returned, whether the whole lifetime is enumerated, or whether a target date filters the 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?

Two front-loaded sentences plus a compact metadata block; every element is load-bearing and nothing is padded. It is arguably too terse for the domain, but there is no wasted wording.

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?

For a tool nested in a family of ~60 dasha endpoints, the level definition and recursion note are the essential differentiators and the output schema covers return values. However, nothing explains what paramayu means to a caller, how this level relates to the antar/prana/sookshma siblings, or what the target-date fields do, leaving gaps an agent must guess at.

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 carries the parameter semantics (birth data, ayanamsa, timezone handling, compact-mode fields/precision) and the description adds nothing to them, which sets the baseline at 3. Notably the description does not touch the targetDate/targetTime window at all, but with full schema coverage that omission is not penalized heavily.

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?

Names the specific dasha level (Kalachakra Pratyantardasha) and defines its depth as a 3-level cascade MD → AD → 9 PDs, which implicitly separates it from the kalachakra_antar (MD→AD) and kalachakra_prana (deeper) siblings. It stops short of explicitly naming or contrasting those siblings, so an agent must infer the ordering from the shared naming convention.

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 when-to-use, when-not-to-use, or alternative routing is given. The cascade notation hints at the level of granularity but never states a condition such as 'use when the question concerns sub-sub-periods rather than Mahadasha-level timing', and no prerequisites (e.g. that a target date drives the period list) are mentioned.

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