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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description's genuine addition is the cost disclosure ('20 credits (Tier 2)') and the group tag, which help an agent budget calls; it adds nothing about output size, depth of the cascade, or computational weight.

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?

Two short lines, front-loaded with the technique name and level before the metadata tags. Nothing is wasted, though the extreme brevity shades into under-specification rather than efficient conciseness.

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 described, but with four near-identical Ashtottari siblings the definition should at least clarify the level hierarchy and what 'pranadasha' yields. 'Finest grain' alone is too thin to let an agent pick correctly among the five cascade levels.

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 schema itself carries rich guidance on birth data, timezone handling, fields/precision compact mode. The description contributes nothing about parameters, so the 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?

It names a specific technique (Ashtottari Pranadasha) and characterizes it as the '5-level cascade (finest grain)', which implicitly distinguishes it from the shallower maha/antar/pratyantar/sookshma siblings. However, it states no verb and never says what is actually computed or returned, so an agent without Vedic dasha knowledge cannot tell what the tool does.

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 explicit when-to-use, when-not-to-use, or named alternative. 'Finest grain' is the only hint that this is the deepest subdivision level, and it is left to the agent to infer that this differs from astroway_vedic_dashas_ashtottari_sookshma.

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