Dashas — Sthira Mahadasha

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

Annotations already indicate readOnly and idempotent. The description adds behavioral details like seed calculation, duration rules, and sub-period splitting, but does not disclose potential errors, edge cases, or output format. No contradiction with annotations.

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 front-loads the tool name and type but then dives into technical details (PyJHora functions, year basis). It is dense and cut off, which reduces clarity. More concise structuring would help.

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 no output schema, the description should explain the return format. It mentions sub-periods but does not describe the response structure, fields, or how results are presented. This is a significant gap for agent invocation.

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% and already explains the birth data parameters. The tool description adds no new parameter information beyond the example request body (which is not in the description proper). It does not clarify the targetDate/targetTime fields from the second object.

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 identifies the tool as 'Sthira Dasha — Jaimini fixed rasi-dasha' and explains the seed calculation. The purpose is specific and distinguishable from other dasha types, though it could more explicitly differentiate from siblings like vimshottari or chara dasha.

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 no guidance on when to use this dasha (e.g., jaimini system vs other systems) or when not to use it. No alternatives are mentioned, leaving the agent without context for selection among many dasha tools.

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