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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context beyond that: the credit cost and Tier 3 pricing plus the aggregation behavior. It says nothing about response size, pagination, or the compact-mode path to shrink output.

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?

One front-loaded sentence that lists the payoff first, followed by compact Group/Cost metadata. No filler, though the sentence is a dense list rather than a scannable structure.

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 need not be explained, and the input schema fully documents all four parameters. The description supplies enough for selection — scope, contents, and cost — leaving only the cost-vs-granular-tool trade-off implicit.

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% and the nested chart object descriptions are extremely detailed (coordinate requirements, timezone rules, houseSystem letters). The description mentions two partners but adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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 concrete verb-plus-resource: a combined Vedic matchmaking report enumerating exactly what comes back (Ashtakoot total, threshold, Manglik check, per-Kuta sub-scores, recommendation). That enumeration implicitly separates it from the granular siblings (astroway_vedic_compatibility_ashtakoot, _manglik_check, _dashakoota), though it never names them.

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?

"in one call" hints that this consolidates what the single-purpose compatibility tools return separately, which is usable routing guidance. But there is no explicit when-to-use/when-not statement and no named alternative, so the agent must infer the trade-off (one 50-credit call vs. several cheaper granular calls).

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