Calculate Vimshottari Dasha

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

Annotations already declare readOnlyHint=true, indicating safe read. The description adds the behavioral trait that the output is 'accepted by report tools', which is useful context. No additional behavioral details, such as performance or input constraints, are provided.

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 description is two concise sentences. The first sentence front-loads the core purpose and outputs. The second sentence adds output format and tool compatibility. No superfluous text.

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's specificity (dasha calculation with 2 params, one required, and no output schema), the description sufficiently explains inputs and output purpose. It could mention that the output includes all periods in one JSON, but overall it is adequate.

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 baseline is 3. The description reinforces that kundali must be from calculate_kundali and on_date is YYYY-MM-DD, but does not add significant new meaning 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?

The description clearly states the verb 'Compute', the resource 'Vimshottari dasha timeline', and specifies the outputs (mahadasha/antardasha periods, running periods). It distinguishes from siblings by focusing on dasha calculation, unlike calculate_kundali (preparation) or generate_report_json (output format).

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 implies usage context by requiring a kundali object and noting the output is for report tools. However, it does not explicitly state when not to use this tool or name alternatives, such as using calculate_kundali first.

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