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

No annotations are provided, so the description carries the full burden. It discloses the computation basis (classical Vedic varga rules) and the return shape, which is useful, but says nothing about permission needs, computational cost, error behavior on invalid D-N codes, or how the birth data is interpreted.

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 labeled sections (WHEN TO USE / WHAT IT DOES / RETURNS) front-load the decision-relevant information and there is no filler prose. The long literal D-N enumeration is the only part that borders on bloat, though it is genuinely useful.

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 9-parameter tool with zero schema coverage and no annotations, the description is incomplete: it never explains that latitude/longitude/timezone default to India-centric values, nor how date/time inputs are interpreted. The output schema exists, so the RETURNS sentence is acceptable rather than necessary.

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 0%, so the description must compensate. It does add genuinely useful syntax for varga_list (comma-separated D-N names with a full example), but leaves the required year/month/day/hour plus latitude, longitude, and timezone_offset completely undocumented in both places.

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?

States a specific verb and resource (calculate divisional/Varga charts) and immediately distinguishes itself from the D-1 baseline produced by calculate_birth_chart. An agent can tell this apart from calculate_ashtakavarga or calculate_yogas without opening any schema.

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 'WHEN TO USE' block gives a clear triggering condition (needs charts beyond D-1) plus concrete examples (D-9 for relationships, D-10 for career). It lacks an explicit negative case or a named sibling alternative, but the boundary against calculate_birth_chart is implied clearly.

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