Dashas — Shodashottari Sookshmadasha

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the agent knows it is a safe computation. The description adds '4-level cascade' implying nesting, but nothing about output format, side effects, or other behavioral traits. Given the annotations, the description contributes minimally.

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 very short, with a clear title line and an example. It is front-loaded and avoids unnecessary words. However, it is almost too terse, leaving out important context.

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 complex tool (4-level cascade dasha with many siblings), the description is incomplete. It does not explain what Sookshmadasha means, what the output looks like, or how it differs from other levels. No output schema exists, so the description should provide more context.

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 the schema already describes all parameters (birth data, target date). The description provides an example request body but does not add meaning beyond the schema's built-in description. Baseline score of 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 states it is a 'Shodashottari Sookshmadasha — 4-level cascade' and places it in the Vedic group. This indicates it is a deep-level sub-dasha, but the purpose is vague: it does not explicitly say it computes dasha periods for a given birth and target date. The example request body provides some clarity, but the purpose could be more specific.

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 provides no guidance on when to use this tool versus the many sibling dasha tools (e.g., antar, prana, pratyantar). There is no mention of when it is appropriate or alternatives, leaving the agent to infer 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.