Dashas: Ashtottari Sookshmadasha

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description does add non-obvious operational context the annotations lack: the POST endpoint and a 20-credit Tier 2 cost, which matters for budgeting. It says nothing about output volume, precision, or what the 'cascade' returns per level.

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?

Three lines, no filler, and the identifying phrase is front-loaded. But the brevity comes from omission rather than economy; the bracket metadata could as easily have been spent on explaining the cascade depth.

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?

For a hierarchical dasha calculator with one required body object and an output schema, the reader still does not know what the four levels are, whether period boundaries or only labels are returned, or how targetDate/targetTime change the result. The output schema excuses explaining return values, but not the missing level semantics.

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 the nested body schema already documents date/time formats, latitude/longitude ranges, ayanamsa, timezone handling and house-system letters in unusual detail. The description adds nothing about parameters, which is acceptable here but earns only the baseline.

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 text restates the tool title ('Ashtottari Sookshmadasha') and adds only the fragment '4-level cascade', which is ambiguous between 'returns four nested levels' and 'is the fourth level'. Nothing distinguishes it from astroway_vedic_dashas_ashtottari_pratyantar or _prana, whose names sit one level away.

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 statement of when to use this versus the other four Ashtottari depth tools, nor any prerequisite about the required birth data. The only selection signal an agent has is the tool name.

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