get_current_dasha

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

With no annotations provided, the description fully bears the burden. It explains the Vimshottari system is 120-year and used for life predictions, adding context that this is a read-only computational tool. However, it does not disclose any error conditions or assumptions (e.g., if data is invalid).

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 sentences, front-loaded with the main purpose and key output details. No fluff. The information about the 120-year system is relevant context.

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?

Given the tool has 5 required parameters (all basic location/birth data), no output schema, and no annotations, the description adequately covers what the tool does and what it returns. It could mention that the calculation requires precise birth data, but overall complete.

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 100%, so the description does not need to elaborate. It adds no extra meaning beyond what the schema provides (e.g., explaining the coordinate format, but this is already in schema descriptions). Baseline score 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 clearly states the tool retrieves the current Vimshottari Mahadasha for a person's birth chart, listing the return fields (ruling planet, start date, end date, remaining years). It distinguishes itself from siblings like get_antardasha or get_dasha_timeline by focusing on the current mahadasha.

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 implicitly indicates use when the current major period is needed, but does not explicitly state when to use alternatives (e.g., get_antardasha for sub-periods, get_dasha_timeline for full schedule). Lacks when-not-to-use guidance.

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