Dashas — Shoola Mahadasha

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

Annotations (readOnlyHint=true, idempotentHint=true) already indicate read-only behavior. The description adds value by detailing the seed calculation, period duration, and sub-period options, disclosing computational behavior beyond the annotations.

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 dense and technical but ends abruptly with 'forward from…' which is incomplete. This lack of completeness harms conciseness and clarity. A more structured format (e.g., bullet points) would improve readability.

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 tool is complex with multiple parameters and no output schema. The incomplete description fails to explain what the tool returns (e.g., list of mahadasha periods). The annotations are good, but the missing output info and truncated description leave gaps for an AI 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?

The schema provides descriptions for all parameters (100% coverage), but the tool description adds significant meaning: it explains the default for 'houseIndex', how the seed is computed, and what each 'antardasaSeedOption' value does. This goes beyond the schema's enum constraints.

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 names the tool as 'Shoola Dasha — Jaimini Trident rasi-dasha' and specifies the seed selection, period length (12 signs forward, 9 years each), and sub-period options. This distinguishes it from sibling tools like 'vedic_dashas_shoola_antar' which handle sub-periods.

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 explains the mechanics but does not explicitly state when to choose this tool over alternatives (e.g., other dasha systems or other shoola levels). Usage context is implied by the name and technical details, but no direct guidance is given.

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