Dashas — Yogini Sookshmadasha

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

Annotations (readOnlyHint, idempotentHint) already indicate safety. The description adds '4-level cascade' hinting at output structure, but does not disclose details like computation behavior, required input fields beyond schema, or that targetDate is essential. No behavioral 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 extremely short (two lines plus example), which is concise but at the cost of clarity. It lacks necessary information to be useful.

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?

Given the complexity of Vedic dashas with multiple levels and cascades, the description is insufficient. It does not explain what '4-level cascade' means, how the sookshma level fits, or what the output contains. No output schema exacerbates this.

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 descriptions already cover the main parameters with 100% coverage. The description includes an example request showing targetDate, which provides minimal additional context but does not explain the semantics of targetDate or the cascade level. Baseline 3 is appropriate.

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 only states 'Yogini Sookshmadasha — 4-level cascade,' which is vague and does not clearly explain that this tool calculates the Sookshma sub-period of the Yogini Dasha. It fails to differentiate from sibling tools like vedic_dashas_yogini_antar or vedic_dashas_yogini_prana.

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 guidance is provided on when to use this tool versus other dashas or sub-levels. There is no mention of prerequisites, alternative tools, or context for selection.

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