Jaimini — Running Dasha Summary

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

Annotations already indicate readOnly, not destructive, idempotent. The description adds little beyond noting the default targetDate, which is a parameter default. No additional behavioral traits or side effects are disclosed.

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 short and includes an example, but the inaccuracy regarding targetDate undermines its conciseness. It could be restructured to correctly map to schema parameters.

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 number of parameters and lack of output schema, the description is incomplete. It does not explain what a 'running Mahadasha' means, the return format, or how to interpret results. The example includes a nonexistent parameter, adding to incompleteness.

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?

The description references a 'targetDate' parameter that does not exist in the input schema, causing confusion. It does not explain any of the 11 actual parameters, and schema coverage is 0%, so the description fails to provide necessary parameter context.

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 it returns the running Mahadasha for Chara, Sthira, and Shoola at a target date. It explicitly calls itself a 'convenience aggregate' and distinguishes from dedicated endpoints. The purpose is specific and unambiguous.

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 provides usage context by noting it aggregates three endpoints into one call, implying it should be used when all three dashas are needed. However, it does not explicitly state when to avoid it or mention alternatives like the dedicated endpoints for single dashas.

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