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 adds genuine behavioral context beyond that: recursion preserves the natal chakra-row and paramayu, which explains how the cascade is anchored. It stops short of describing the return shape or any auth/rate-limit behavior.

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 tight sentences plus a group/cost footer; nothing is padded, and the operative detail (cascade depth, preserved natal parameters) is front-loaded. Slightly terse relative to the domain jargon it assumes.

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?

With an output schema present and 100% input-schema coverage, the description needn't explain return values or fields. What remains missing is selection guidance against the many sibling dasha tools, which is the main decision an agent faces here.

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 fully documented in the schema (including the compact-mode semantics). The description adds no parameter-level information, which is the expected baseline when the schema does the heavy lifting.

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 names the exact dasha level and its depth ('3-level cascade (MD → AD → 9 PDs)'), which is more specific than the bare title and distinguishes it from the shallower antar/maha siblings in the Kalachakra family. It does not, however, name the sibling tools it differs from, so differentiation is left to the agent's inference from the level terminology.

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 and no mention of alternatives such as kalachakra_antar, kalachakra_prana, or another dasha system's pratyantar. The agent must guess at the appropriate depth level from the name alone.

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