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 genuinely useful non-schema facts: the endpoint and a 20-credit Tier 2 cost, which matters for budgeting. It says nothing about the computed output's nature or depth, so it is adequate rather than rich.

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?

Four short lines, front-loaded with the technique name and the cascade depth, then bracketed metadata. Nothing is padded, though the body is closer to a label than a description.

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 schema carries the full input contract. However, for a niche nested dasha in a family of roughly sixty dasha siblings, an agent gets no help on what '4-level cascade' yields or how sookshma differs in granularity, leaving the routing decision underspecified.

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 birth-data block documents date/time/latitude/longitude, timezone handling, ayanamsa and houseSystem in detail, plus the fields and precision compaction params. The description adds no parameter meaning at all, so the baseline 3 for a fully documented schema 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?

Names the specific technique (Kalachakra Sookshmadasha) and its shape (4-level cascade), which distinguishes it from the Kalachakra maha/antar/pratyantar/prana siblings and from other dasha families. It stops short of an explicit verb or of stating what the tool returns, so it is clear but not fully self-routing.

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 statement of when to pick sookshma over prana or pratyantar, no prerequisites, and no named alternative. The agent must infer the usage tier purely from the name suffix.

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