Dashas — Vimshottari Mahadasha

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

Annotations already indicate a read-only, idempotent operation. The description adds behavioral context about the computed sequence, truncation of the first period, and the reliance on birth data. It does not contradict annotations and provides useful logic details beyond structural hints.

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 concise, using only a few lines to convey essential information. It is front-loaded with the core functionality and includes group/cost details without unnecessary wording.

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 tool's complexity and lack of output schema, the description provides the core algorithm but omits what the response looks like (list of periods). While adequate, it could be slightly more complete by mentioning the return format.

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 description adds value by clarifying that lat/lon/tz default to 0 and that real values are needed for accuracy, plus an example request. This context helps the agent understand parameter usage beyond the schema.

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 the tool computes the 'Canonical Vimshottari Mahadasha sequence' with specific details like the 9 planets, 120-year cycle, and the rule based on Moon's nakshatra. It distinguishes itself from other dasha tools in the sibling list by focusing solely on Vimshottari Mahadasha.

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 does not explicitly guide when to use this tool versus alternatives like sub-period dashas or other dasha systems. It implies usage through the name and context, but lacks explicit 'when to use' or 'when not to use' instructions.

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