Dashas: Shoola Pratyantardasha

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the endpoint and the 20-credit Tier 2 cost, which is real behavioral context, but it does not explain the returned structure or any rate limits.

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 compact and front-loads the dasha name and level. There is no filler, though the first sentence is under-specified rather than genuinely informative.

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 Vedic dasha tool with an output schema and dozens of similar siblings, the description omits what Shoola dasha is, what the three levels mean, and how the output should be interpreted. The endpoint and cost are present, but an agent lacks enough context to confidently choose this tool over shoola_antar or another pratyantar variant.

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 schema itself extensively documents the single body parameter, including required birth data, timezone behavior, and houseSystem semantics. The description adds no parameter meaning beyond what the schema already provides, so the baseline 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 restates the tool title ('Shoola Pratyantardasha') and adds only '3-level cascade'. It names no verb such as calculate, list, or return, and does not distinguish this tool from sibling dasha levels like shoola_antar, shoola_maha, shoola_prana, or from pratyantar tools in other dasha systems.

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?

There is no guidance on when to invoke this tool versus alternatives. The sibling set contains several closely related shoola dasha levels and many pratyantar variants for other dasha systems, but the description does not say when this particular level is appropriate.

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