get_dasha_timeline

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

Description explains output structure with periods and durations, which adds context. No annotations provided, so description carries burden. Could mention return format details.

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?

One sentence, front-loaded with purpose. Slightly long due to listing periods, but necessary for clarity.

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 5 required params, no output schema, and no annotations, description covers purpose and output well. Could mention ordering or typical use case.

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 has 100% coverage with descriptions for all 5 parameters. Description adds context about output (periods) but doesn't repeat param details. Slight value add.

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?

Description clearly states it gets a 120-year Vimshottari Mahadasha sequence from birth, listing all 9 planetary periods with durations. It distinguishes from siblings like get_current_dasha and get_antardasha.

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?

Description implies use for full timeline, but doesn't explicitly say when not to use or name alternatives like get_current_dasha for current period only.

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