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 useful non-annotation context — the group (Vedic) and the cost (20 credits, Tier 2) — but says nothing about what the cascade returns or how deep it descends.

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 short lines with no waste, and the tool identity plus cost are front-loaded. However, the brevity is under-specification rather than efficiency: the core '4-level cascade' claim is left unexplained.

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 schema (100% coverage) and an existing output schema, the description needn't explain params or return values. But against ~45 sibling dasha variants in the same family, it fails to position the tool at all — an agent cannot tell from this text what a Sthira Sookshmadasha adds over the antar/pratyantar/maha 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?

Schema description coverage is 100%, and the rich nested schema documents birth data, timezone handling, fields, and precision in detail. The description adds no parameter guidance, which is acceptable given the schema does the heavy lifting; 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 title/name ('Sthira Sookshmadasha') and adds an opaque phrase '4-level cascade' that does not explain what the tool computes or returns. It never says this is a Vedic dasha period calculation, nor does it distinguish this level (sookshma) from the maha/antar/pratyantar/prana siblings that share the same base name.

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 indication of when to call this vs. the alternative levels (antar, pratyantar, prana) or vs. other dasha systems (vimshottari, ashtottari, chara, etc.). '4-level cascade' hints at depth but gives no rule for choosing this tool.

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