Calculate Kundali (Birth Chart)

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

The description discloses detailed output (lagna, Moon rashi, navamsa, etc.) and states the return format is JSON consumed by other tools. The annotations already indicate readOnlyHint=true, and the description adds significant behavioral context beyond that.

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 two sentences, front-loaded with purpose, and every sentence adds value. No wasted words.

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?

The description fully explains the outputs and their consumption by other tools, compensating for the lack of output schema. It gives a complete picture of the tool's role in the workflow.

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 coverage is 100%, so the description does not need to elaborate on parameters. The description adds overall context but no per-parameter extra meaning beyond what the schema provides, meeting the baseline for high coverage.

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 the tool computes a sidereal Vedic kundali from birth details, enumerates specific outputs (lagna, Moon rashi, etc.), and mentions the output is consumed by other tools. It distinguishes itself from siblings by specifying the relationships with dasha, gochar, compatibility, and report 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?

The description implies the tool is used to compute the initial birth chart for downstream tools, and the sibling tool list provides context. However, it does not explicitly state when to use this vs alternatives or when not to use it, lacking explicit guidance.

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