Dashas — Sthira Pratyantardasha

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds no behavioral context beyond what is in the annotations; it does not mention what the tool computes or returns.

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 very short (one line plus an example). It lacks structure such as separate sections for usage, parameters, or output. The example is helpful, but overall it is too minimal.

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?

There is no output schema, and the description does not explain what the tool returns (e.g., a list of periods, dates, effects). Given the large number of sibling dasha tools, the lack of output context makes it hard to understand the tool's role.

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% (the body parameter includes descriptions for sub-fields). The example request body provides a usage pattern but does not add semantic meaning beyond the schema. Baseline 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 name and title clearly indicate it's a Vedic dasha sub-period (Sthira Pratyantardasha), and '3-level cascade' hints at its nature. However, it does not explain what a pratyantardasha is or how it differs from other dasha levels (e.g., antar, prana), making it hard for an unfamiliar agent to distinguish among many sibling tools.

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 on when to use this specific sub-period versus other dasha tools (e.g., vedic_dashas_sthira_antar, vedic_dashas_sthira_maha). The sibling list contains many similar tools, and the description offers no criteria for selection.

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