vedic_chart

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

Annotations declare readOnlyHint=true and destructiveHint=false. The description adds that the tool costs 1 credit per call and explains return content (planet placements, nakshatras, etc.), providing behavioral context beyond 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 five sentences organized into a purpose statement, credit cost, supported ayanamsa, and example. It is clear and well-structured, though could be slightly more concise.

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 explains return values (planet placements, nakshatras, bhavas) and mentions houses system (Whole Sign). It covers credit cost and ayanamsa options. Some additional detail on output structure would improve completeness.

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 input schema has 100% parameter description coverage. The description adds value by listing supported ayanamsa values with default, and provides an example illustrating use of datetime, latitude, and longitude.

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 calculates a Vedic natal chart with specific outputs (planet placements in rashis, nakshatras, navamsa, bhavas), using a distinct verb 'Calculate' and resource. It distinguishes from sibling tools like ephemeris_natal_chart which use tropical zodiac.

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 usage for Vedic astrology but does not explicitly state when to use this tool versus alternatives (e.g., Western chart tools). It lacks guidance on prerequisites or exclusions.

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