Vedic Divisional Chart (DEPRECATED — use /vedic/varga/{D}<*>)

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

Adds context beyond annotations: deprecation timeline (6-month sunset), credit cost (20 credits), group label, and zodiac type. Annotations already indicate read-only, non-destructive, idempotent behavior; description aligns and provides additional operational details.

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?

Description is relatively brief but well-structured: deprecation notice, replacement link, group, cost, example, and warning. Some redundancy (DEPRECATED appears twice), but overall each sentence serves a purpose. The example is clearly formatted.

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 deprecated tool, the description covers essential context: what it does, how to call it (with example), and why to avoid it. No output schema is provided, but the description does not need to detail return values given deprecation and alternative endpoints. It sufficiently informs agent decision-making.

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%, baseline 3. Description adds value by showing a complete example request and highlighting the 'varga' parameter semantics (e.g., 'D9 Navamsha'). It also clarifies defaults for lat/lon/tz. These details go beyond the schema's field descriptions.

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 it calculates a Vedic divisional chart using sidereal zodiac, and prominently marks it as DEPRECATED with a replacement recommendation. This provides a specific verb-resource pair and distinguishes from sibling per-varga endpoints.

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?

Explicitly advises against using this tool ('Avoid using') and directs the agent to dedicated per-varga endpoints. Also specifies supported vargas (D1–D60) and provides an example request body, giving clear guidance on when and how to use.

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