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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description genuinely adds non-annotation context: the endpoint, the required inputs and a 20-credit Tier 2 cost, which matters for an agent budgeting calls. It does not describe result depth or failure modes, so it stays at a moderate score.

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?

Front-loaded two-sentence core followed by a tight bracketed metadata block; nothing is padded. The brevity is appropriate, though the metadata block is doing work the prose should arguably do.

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 15-parameter tool with low schema coverage, the description omits selection guidance against three competing Pitra/Pitru siblings and explains none of the optional parameters. An output schema exists so return values need not be covered, but the input-side and routing gaps leave it under-specified.

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 a compensation burden it does not meet. It merely restates the four required fields already marked required in the schema and adds no semantics for city, name, cosmogram, zodiacType, houseSystem or ayanamsaId.

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?

Names the specific dosha (Pitri Rin / paternal-debt) and the interpretive school (Lal Kitab), plus states the deliverable (triggers + remedy). This meaningfully separates it from sibling pitfalls like astroway_vedic_doshas_parashara_pitru and astroway_vedic_doshas_kp_pitra. It lacks an explicit verb ('compute'/'analyse'), so it's clear but marginally less crisp than 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?

There is no when-to-use guidance and no named alternative, despite a dense sibling set of Pitra/Pitru tools across KP, Parashara and Lal Kitab schools. The only guidance is the required-parameter list and cost, which is operational rather than selection-oriented.

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