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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful operational context beyond that: the cost (20 credits, Tier 2), the endpoint, and the fact that a KP Moon sub-lord chain is attached to the result. It does not describe error or edge-case behavior, hence not a 5.

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 with the yoga's defining condition, followed by compact bracketed metadata (group, endpoint, required, cost). Every element carries information and there is no filler, though the [Required] line duplicates the schema's required array.

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 no explanation, and annotations carry the safety profile. For a single-dosha detector the description supplies the condition, the flag meaning, the cost and the endpoint, which is enough for correct invocation; the main gap is that no alternative/aggregate sibling is named.

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% (low), so the description is expected to compensate, but it does no more than restate the four required parameters already declared in the schema. It adds no meaning for ayanamsa, zodiacType, houseSystem, timezone, precision, fields, or the remaining optional inputs, leaving half the surface 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?

The description states a precise computed condition (no planet excluding Sun/Rahu/Ketu in 2nd or 12th from Moon) and labels the output as a Moon-isolation flag with an emotional/financial volatility indicator. That is a specific verb+resource that an agent can match to the request 'check Kemadruma'. It does not explicitly distinguish itself from the aggregate sibling astroway_vedic_doshas_kp_full, which is the only reason it is not a 5.

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?

Usage is implied by the yoga definition rather than stated: an agent can infer it should call this when a user asks specifically about Kemadruma, but there is no explicit 'use X instead of Y' or exclusion against the kp_full aggregate sibling. No prerequisites or when-not conditions are given.

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