Dashas: Shatabdika Pratyantardasha

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful operational context beyond the annotations: the POST endpoint and the 20-credit Tier 2 cost. It does not describe what the response contains or how the cascade periods are ordered, though an output schema exists.

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 core capability sentence is front-loaded and short, with no filler prose. The bracketed Group/Endpoint/Cost metadata is boilerplate but functional; it does not obscure the purpose.

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?

Safety is covered by annotations, inputs by a fully described schema, and return shape by an output schema, so the tool is callable. What is missing given the enormous sibling set is any disambiguation of this depth level from the maha/antar/prana/sookshma variants of the same dasha school.

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 there is effectively one body parameter, so the schema carries all parameter meaning: birth data, timezone/offset handling, ayanamsa, houseSystem and optional targetDate/targetTime. The description adds nothing about parameters, which is acceptable at baseline 3 given the richness of 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 names the specific technique (Shatabdika Pratyantardasha) and states the computation: a 3-level cascade of Mahadasha → Antardasha → 7 Pratyantardashas. That is a concrete verb+resource statement. It does not explicitly contrast with the shatabdika_maha/antar/prana/sookshma siblings, though the level is inferable from '3-level cascade'.

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 choose this over astroway_vedic_dashas_shatabdika_antar, _prana or _sookshma, and no prerequisites or exclusions are stated. The agent must infer the selection from the tool name and the depth phrase alone.

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