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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description usefully adds that each rin returns trigger conditions plus a recommended remedy, and discloses the 20-credit Tier 2 cost, which annotations do not. It omits any auth, rate-limit, or empty-result behavior.

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?

Three tightly written sentences plus structured [Group]/[Cost] tags, front-loaded with the tool's identity and output. No filler, though the source-attribution sentence (K. Ashant Vol. IV + R.D. Mathur) is only marginally useful to an invoking agent.

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-value explanation is not strictly required, and annotations cover the safety profile. But for a 15-parameter tool at 33% coverage with a near-duplicate sibling, the description leaves parameter requirements and sibling disambiguation unaddressed.

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 only 33% across 15 parameters, so the description carries the burden of compensating and does not. It never mentions that date, time, latitude, and longitude are required birth-chart inputs, nor the ayanamsa/houseSystem/compact-mode (fields, precision) options that the schema only partially documents.

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?

Specific verb 'Detects' plus a named resource (six ancestral debts, each enumerated: Pitri/Stree/Kanya/Atma/Rishi/Daiva Rin) with a stated method (Lal Kitab planet-affliction patterns). However, it does not distinguish itself from the near-identical sibling astroway_vedic_doshas_lal_kitab_rin, so an agent cannot tell the two apart from the text 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?

The description gives no when-to-use guidance, no prerequisites, and names no alternative. With a direct sibling (vedic_doshas_lal_kitab_rin) and a related lal_kitab_full tool in the list, 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.