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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description goes beyond with rich detail: it discloses that the output includes start/end dates for every level, hour-level timing, remaining time per level, the optional KP significators payload, dependence on birth Moon nakshatra, and selectable Lahiri/KP ayanamsa. This is genuinely useful context about what the computation does and what the response will contain.

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 first sentence is well front-loaded with the core five levels and remaining time. However, phrases like 'Accurate dasha calculator API for life phase prediction and planetary period analysis' and 'Essential for understanding current planetary influences...' are promotional and not technically necessary; they repeat the tool's purpose without adding new behavioral information.

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 12 parameters, no output schema, and many sibling dasha tools, the description gives enough about the returned timeline (start/end dates per level, hour-level timing, remaining time, optional KP significators) for an agent to invoke it correctly. The key gap is again the lack of explicit contrast with sibling dasha tools, but this is mostly made up for by the word 'current' in the name and description.

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?

Input schema coverage is 100% and every parameter has a detailed description already. The description adds minor semantic reinforcement (e.g., 'set significators true' expands the output, ayanamsa selection) but does not meaningfully compensate or go beyond that schema. Baseline 3 is appropriate.

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 explicitly names the five Dasha levels (Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana) and the specific verb 'Calculate... with remaining time in each.' It clearly identifies this as the tool for the current running Vimshottari Dasha timeline, distinguishing it from sibling tools that cover individual historical dasha levels (major, sub-mahadasha, antardasha, etc.).

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?

The description gives a clear use-case: 'Essential for understanding current planetary influences, dasha transitions, and timing events in Vedic astrology.' However, it never explicitly says when NOT to use it or when to use sibling dasha tools such as post_vedic_astrology_dasha_major or the other sub-dasha variants. Usage is implied through the word 'current' but alternatives are not named or contrasted.

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