Dashas — Shodashottari Antardasha

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

Annotations declare readOnlyHint=true, and the description adds algorithmic detail ('Recursive proportional split (parent_years × sub_planet_period / 116)'). However, it does not disclose return format, side effects, or other behaviors beyond the formula.

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 concise: two sentences and an example. It front-loads the purpose and formula without unnecessary text.

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?

The description explains the algorithm and number of sub-periods, but lacks any description of the return value (no output schema). Given the complexity of dasha calculations and many sibling tools, more detail on output format would improve completeness.

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%, and the description provides an example request body. This adds some value but does not explain each parameter beyond the schema's built-in descriptions.

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 computes the Shodashottari Antardasha, which consists of 8 sub-periods of the running mahadasha at a target date. It includes the formula and distinguishes itself from other dasha tools by specifying the system and level (antardasha).

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 vedic_dashas tools (e.g., vimshottari, ashtottari). The agent must infer based on the name and system alone.

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