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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add operational context. It does disclose the cost (20 credits, Tier 2) and the endpoint, which are genuinely useful for an agent budgeting calls, but says nothing about failure modes, data requirements, or interpretation limits.

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 dosha definition and its astrological condition, then a compact bracketed metadata block for group, endpoint, required inputs and cost. Every line is short and scannable with no filler prose.

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 required, and the required inputs plus cost are covered. What is missing is the routing context an agent needs in a catalogue of ~160 sibling tools: why choose this Parashara Shrapit endpoint over the KP, Lal Kitab, or full-dosha variants.

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% (10 of 15 params undocumented, including date, time, latitude, longitude, city, name, zodiacType, houseSystem, ayanamsaId, cosmogram). The description merely restates the required set that the schema's 'required' array already lists, so it does not compensate for the uncovered optional parameters an agent must reason about (e.g. ayanamsaId, zodiacType, houseSystem).

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 names a specific dosha and gives its astronomical definition (Saturn + Rahu conjunct in any sign), so an agent knows exactly which condition this tool evaluates. It stops short of differentiating itself from the closely named siblings (astroway_vedic_doshas_kp_shrapit, astroway_vedic_doshas_lal_kitab_shrapit, astroway_vedic_doshas_parashara_full), leaving the 'Parashara' scope to be inferred from the name.

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 at all: nothing says when to call this single-dosha endpoint versus astroway_vedic_doshas_parashara_full, or how it relates to the KP and Lal Kitab Shrapit variants. The only context given is group/endpoint/cost metadata, which is not usage guidance.

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