Dashas — Ashtottari Sookshmadasha

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds only group and cost information, not behavioral traits like computation constraints, error handling, or the meaning of the 4-level cascade. The agent gains no additional transparency beyond 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 very short (two sentences plus example and group/cost line). It is concise but at the expense of clarity and completeness. While efficient, it sacrifices explanatory content.

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 is part of a complex family of dasha calculators with no output schema, the description fails to explain what the tool returns (e.g., dates, periods). The '4-level cascade' is not elaborated, and the agent lacks enough context to understand the tool's output or usage sequence.

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 schema already describes the required fields. The description provides an example request body but no further elaboration on parameter meanings or constraints. Baseline of 3 is appropriate as the description adds minimal value.

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 states 'Ashtottari Sookshmadasha — 4-level cascade', which hints at the tool's function but does not clearly explain that it calculates the fourth-level sub-period within the Ashtottari Dasha system. The example provides a request body but lacks explicit purpose. It distinguishes itself from siblings only by name, not through a clear description.

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 is provided on when to use this tool versus other dasha tools (e.g., antar, prana). There is no mention of prerequisites or context for usage, leaving the agent without direction on appropriate scenarios.

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