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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the genuinely useful cost metadata (20 credits, Tier 2) and group membership, but says nothing about what the cascade output contains or how deep/temporally bounded the periods are.

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 identifying phrase, and the cost/group tags are informative rather than filler. It is efficient, though partly because it says so little.

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?

With a rich input schema and an output schema present, parameter and return-value explanation is not needed, so the definition is workable. The remaining gap is sibling disambiguation across the dense dasha family, which the tag line does not address.

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%, including detailed prose on date/time/latitude/longitude, timezone semantics, ayanamsa, houseSystem letters, plus 'fields' and 'precision' compact-mode params. The description adds no parameter meaning whatsoever, 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?

The description names the exact dasha system (Shatabdika) and the specific level (Pranadasha), and '5-level cascade (finest grain)' distinguishes it from the shallower shatabdika_maha/antar/pratyantar/sookshma siblings sharing the namespace. It stops short of a full verb phrase ('computes a dasha timeline'), but an agent can place it correctly among the ~50 dasha siblings.

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 guidance at all: nothing says when a Prana-level Shatabdika breakdown is preferable to Sookshma or Pratyantar, or how this system differs from Vimshottari/Ashtottari. The agent must infer routing purely from the tool name.

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