Calculate Kundali (Birth Chart)

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

Annotations declare readOnlyHint=true and openWorldHint=false. The description adds valuable behavioral context: it is a computation that returns a complex JSON object consumed by other tools. No destructive behavior is implied, and there is 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 is a single, coherent sentence that packs significant information without being verbose. It is front-loaded with the core action and outputs.

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?

Despite lacking an output schema, the description enumerates the major components of the return value (lagna, Moon rashi, nakshatra, planet positions, navamsa, divisional charts, ashtakavarga, Vimshottari dasha seed) and explains its role in the tool ecosystem. For a tool of this complexity, this is thorough.

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%, so the baseline is 3. The description adds value by explaining the overall purpose and listing the computed outputs, but it does not provide additional detail for individual parameters beyond what the schema already describes.

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 specific verbs and nouns: 'Compute a sidereal Vedic kundali' and lists the outputs (lagna, Moon rashi, etc.). It distinguishes from sibling tools like calculate_dasha and calculate_gochar by stating that its output is consumed by those 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 that this tool should be used first before other kundali-dependent tools (dasha, gochar, compatibility, report) by stating it returns the JSON they consume. It does not explicitly state when not to use it, but the context is clear.

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