Dashas: Shoola Sookshmadasha

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 genuinely useful operational context the annotations do not: the POST endpoint, the Vedic group, and a 20-credit Tier 2 cost that an agent should weigh before calling. It says nothing about pagination, response size, or what the cascade contains, so a 3 rather than a 4.

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?

One content sentence plus three bracketed metadata lines; no filler and the identifying information is front-loaded. Brevity here is close to under-specification rather than padding, so it earns a 4, not a 5.

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?

An output schema exists, so the description need not explain return values, and annotations cover safety. What remains missing is the core conceptual content: what a Shoola sookshma period represents and how the four cascade levels relate, which matters for a niche Vedic tool whose siblings differ only by level name.

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 single body parameter has 100% schema description coverage, including detailed guidance on timezone vs timezoneOffset, houseSystem letters and ayanamsa. The description adds nothing about parameters, but the schema does the heavy lifting, so baseline 3 applies.

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?

"Shoola Sookshmadasha: 4-level cascade" names the exact dasha system and level, and "4-level cascade" hints that the response nests several sub-levels. But it only restates the title plus a fragment; it never says what a sookshma dasha is or what period/planet sequence the tool computes. An agent without Vedic domain knowledge cannot tell what it gets back beyond "a 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 statement of when to pick this over astroway_vedic_dashas_shoola_maha, _antar, _pratyantar or _prana, which are the direct alternatives. The only differentiator is the word "sookshma" embedded in the name, leaving the agent to infer the level hierarchy from naming convention alone.

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