Dashas — Kalachakra Pratyantardasha

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

The description adds behavioral context beyond annotations by noting that recursion preserves the natal chakra-row and paramayu. Annotations already indicate read-only, non-destructive, idempotent behavior. No contradictions.

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?

The description is two sentences plus an example, front-loaded with purpose and key behavioral note. Every element earns its place with no wasted words.

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?

While annotations and schema cover safety and parameters, the description omits output structure or further interpretation guidance. For a complex 3-level dasha tool, this is adequate but leaves gaps for an agent.

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 coverage is 100%, so baseline is 3. The example request body provides a concrete usage pattern but does not explain parameters beyond what the schema describes.

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 clearly states it is Kalachakra Pratyantardasha with a 3-level cascade (MD→AD→9 PDs), distinguishing it from sibling tools like vedic_dashas_kalachakra_maha and vedic_dashas_kalachakra_antar.

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?

The description implies usage for Kalachakra Pratyantardasha calculations but provides no explicit guidance on when to use this tool versus other dasha systems (e.g., Vimshottari, Ashtottari) or alternatives.

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