Dashas — Tribhagi Sookshmadasha

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds no behavioral context. The phrase '4-level cascade' is vague and does not explain what the tool returns or any side effects.

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 very short (one line plus an example), which is concise but at the cost of completeness. It is front-loaded with the title and description, but the lack of essential information makes it insufficient.

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?

There is no output schema, and the description does not explain what the tool returns. Among many sibling dasha tools, the description fails to differentiate this one's output or use case. The example only covers input, not output.

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 schema already provides detailed descriptions for the input body and its fields, covering 100% of parameters. The description adds an example request, which is helpful for formatting but does not add new meaning beyond the schema.

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 'Tribhagi Sookshmadasha — 4-level cascade' hints at the function but lacks an explicit verb like 'calculates' or 'returns'. The example request provides context, but the purpose is not clearly stated, leaving ambiguity among sibling dasha tools.

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?

No guidance is given on when to use this tool versus alternative dasha levels (e.g., mahadasha, antardasha, pratyantardasha). The description does not mention prerequisites, exclusion criteria, or sibling tools.

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