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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, non-open-world), so the bar is lower. The description usefully adds the return contents (per-Kuta scores, Bhakoot/Nadi dosha flags, threshold verdict) and the 50-credit Tier 3 cost, which annotations do not convey. It does not disclose any hidden constraints 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 definition is front-loaded, dense and essentially waste-free: identity, scoring breakdown, interpretation thresholds, and return shape. The [Group]/[Cost] tags are boilerplate but short and placed last.

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?

An output schema exists, so return values needn't be spelled out, and the description still summarizes them adequately. For a two-chart, cost-bearing tool with rich nested input, the only meaningful omission is differentiating it from the other Vedic compatibility siblings.

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 nested chart1/chart2 objects, fields, and precision are already documented in detail by the schema. The description adds nothing about input format or the meaning of individual parameters. Baseline 3 is appropriate when the schema carries the full burden.

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 gives a specific verb+resource (8-Kuta matchmaking scored out of 36) and even enumerates the eight Kutas with their point weights. That is far more precise than a tautology. It stops short of explicitly distinguishing itself from the clustered compatibility siblings such as astroway_vedic_compatibility_dashakoota or _full, which an agent would have to infer from the name alone.

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?

There is no statement of when to use this versus alternatives, no prerequisites, and no excluded cases. The score-threshold sentences interpret a result rather than guide tool selection. With several near-identical Vedic compatibility siblings, the absence of routing guidance is a real gap.

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