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

Annotations already declare this a safe, idempotent, non-destructive read (readOnlyHint, idempotentHint, destructiveHint=false), so the safety profile is covered. The description adds the cascade depth and sub-period duration, plus cost metadata, but says nothing about output shape, computational load, or the fact that it needs birth data.

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 terse lines, front-loaded with the definition, with group and cost as bracketed metadata that an agent can skim. Every element earns its place; no filler.

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 annotations cover safety. However, the description omits that the tool requires a full birth chart (date, time, coordinates, timezone), which is the main prerequisite for calling it, leaving that burden entirely to the schema.

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%, so the body/fields/precision parameters are already fully documented in the schema, including the detailed birth-data and timezone semantics. The description adds nothing beyond that, 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?

States a specific verb-resource pair (Vimshottari Pranadasha) and pins its place in the hierarchy as the '5th-level Dasha, the finest grain,' which separates it from sibling levels like sookshma, pratyantar, antar and maha. It does not name the closest sibling (vimshottari_sookshma) explicitly, but the level ordinal does the differentiation work.

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 or when-not-to-use guidance is given. The duration hint ('a few hours to a few days') implies the granularity of interest, but the description never says to choose this over pratyantar or sookshma, nor what question it answers. An agent must infer selection from the level number alone.

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