Dashas: Shodashottari Sookshmadasha

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 adds genuinely new context: the per-call cost (20 credits, Tier 2) and that the output is a four-level cascade. It does not contradict the annotations, but says nothing about what the cascade levels contain or how targetDate/targetTime influence the result.

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?

It is short and front-loads the one substantive fragment, but most of the text is bracketed metadata (group, endpoint path, credit tier) rather than user-facing guidance. Efficient in length, yet the space is spent on plumbing instead of disambiguation.

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 return values need not be explained, and the input schema is rich. But for a tool whose whole meaning is its position in a five-level dasha hierarchy, the description never defines sookshma, never explains the targetDate/targetTime forward-looking fields, and never helps pick among near-identical siblings.

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?

There is a single body parameter whose schema is fully documented at 100% coverage, including detailed notes on timezoneOffset, ayanamsa, houseSystem letters, and rejected short forms. Per the rubric this makes the schema the authority; the description adds nothing about the parameters, 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?

The description essentially restates the tool name and title ("Shodashottari Sookshmadasha") and appends the fragment "4-level cascade." That fragment is the only content implying what the tool computes, and it never says sookshma is the fourth subdivision level or how it differs from the sibling shodashottari_maha/antar/pratyantar/prana 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 when-to-use, when-not-to-use, or alternative is named, despite roughly ten sibling dasha tools at different cascade depths. An agent has no way to decide between shodashottari_sookshma, _prana, _pratyantar, or a different dasha system from this text.

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