divine_get_shani_ashtam_shani

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds meaningful behavioral detail by specifying what is computed: transit periods of Saturn in the eighth from natal Saturn, natal Saturn placement, the ashtama sign, and age-banded predictive content. No contradiction with the annotations exists.

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 compact: the first sentence states the operation, and the second lists the return content. Every sentence earns its place, with no filler or irrelevant background.

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?

For a read-only, idempotent lookup with a bundled birth-detail input object and an output schema, this description is complete enough for an agent to invoke it correctly. It explains the computation and the returned components, while annotations and schema cover safety and parameter details.

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 does not add meaning to the single 'params' parameter beyond saying 'for a birth chart.' However, the referenced KundliInput schema thoroughly documents every birth field with examples, so the agent still has strong parameter guidance from the schema itself.

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 uses a specific verb and resource: 'Get the Ashtama Shani analysis for a birth chart.' It goes further and defines the exact astronomical condition (transiting Saturn in the eighth house from natal Saturn), which makes the tool unambiguous even among many sibling Vedic astrology 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?

There is no explicit guidance on when to use this tool versus alternatives such as divine_get_sadhe_sati or divine_get_chandrashtama. The intended use is only implied by the tool name and the phrase 'for a birth chart'; no exclusions, prerequisites, or comparison to siblings are provided.

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