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 fully covered structurally. The description contributes real additional signal: the endpoint and a concrete cost (20 credits, Tier 2), which matters for an agent budgeting calls. It does not add anything about result shape or latency, but with annotations carrying the behavioral burden a 3 is appropriate.

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 compact lines, front-loaded with the identity of the dasha and its grain, followed by terse bracketed metadata. Every element earns its place with no prose padding, though the metadata block is more catalog-style than explanatory.

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 input schema is exhaustive. The gap is routing context: as one of ~60 near-identical dasha tools, the description does not tell an agent how to pick this level over its siblings, leaving completeness at minimum-viable.

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 richly documents date/time/latitude/longitude, ayanamsa, timezone, houseSystem, plus fields/precision. The description adds nothing about parameters, so baseline 3 applies since the schema does all the work.

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 states a specific resource (Sthira Pranadasha) and qualifies it as a '5-level cascade (finest grain)', which distinguishes it from the coarser sthira_maha/antar/pratyantar/sookshma siblings. However, the verb is implicit (compute/list) and it leans on the reader knowing the dasha-level hierarchy rather than spelling out that this returns the finest sub-period subdivision.

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 level versus the adjacent sthira levels or the many parallel dasha systems (vimshottari, ashtottari, yogini, etc.). The '(finest grain)' hint implies a use case but no explicit when/when-not or alternative is named.

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