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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive behavior beyond them: dates are in IST, results cite Phaladīpikā ch. 26 per verse, both Moon signs are handled where a star spans two, and the reading is explicitly general rather than individual. It does not discuss caching, rate limits, or error behavior, but the transparency is well above the annotation baseline.

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?

The purpose and scope are front-loaded in the first clause, followed by the contents and then a compact parameter glossary. The prose is dense and sentence-long but every clause carries information about what is returned or accepted.

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 re-explained; the description still adds the structural detail an agent needs (what sections the forecast contains, IST dating, dual Moon-sign handling) plus full parameter value guidance. Nothing essential for correct invocation appears to be missing.

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 coverage is 0%, so the description must carry all parameter meaning, and it does: birth_star is any of the 27 nakshatras acceptany common spelling, ascendant is a sign in English or Sanskrit, and month is 'current' or 'next' — supplying value-space information the schema's plain string types lack.

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 a specific verb and resource: a monthly Vedic transit forecast for a given birth star and ascendant, enumerating the delivered artifacts (planetary moves with dates, house crossings, classical results, tārā). It clearly differs from siblings like panchang or festivals by output content, but it never explicitly names or excludes those 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?

Usage is implied — you call it when you want a month-scoped forecast for a star/ascendant combination — and it notes the reading is 'general ... for reflection' rather than personalized. However, there is no explicit when-to-use/when-not guidance and no routing to panchang, festivals, or find_birth_star.

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