get_antardasha

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

No annotations provided, so description must cover behavioral traits. It states the tool provides finer timing and each Mahadasha is divided into 9 sub-periods, which is helpful. However, it does not describe side effects, data source, or whether calculations are based on a specific system (e.g., Vimshottari). A 3 is adequate.

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?

Very concise: two sentences that efficiently state the tool's purpose and provide helpful context about the 9 sub-periods. No wasted words.

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?

For a tool with no output schema, the description gives a clear picture of what it does and provides context about the 9 sub-periods. Given the complexity of the domain, it is complete enough.

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 description adds minimal value beyond what the schema already provides for parameters. The description does not add additional meaning to any parameter beyond the schema descriptions.

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?

Clearly states it gets Antardasha (sub-periods) within a Mahadasha. The verb 'get' and resource 'Antardasha' are specific. Differentiates from sibling tools like get_current_dasha and get_dasha_timeline by focusing on sub-periods.

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?

Implies usage when finer timing is needed within a Mahadasha, but does not explicitly state when to use this versus other dasha tools. No exclusions or alternatives are mentioned.

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