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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context — the credit cost (20 credits, Tier 2) and the Vedic grouping — but says nothing about what the computation consumes or how heavy it is. Adequate given the annotation coverage, but not rich.

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?

Tightly front-loaded: the core statement comes first, followed by compact group/cost metadata tags. No wasted words, though the extreme brevity is arguably under-specification rather than efficiency.

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 chart-calculation tool with no annotations covering inputs, the description is too thin: it does not say what birth data is needed, that the result is KP-flavored (implying ayanamsa choice), or what distinguishes its output from the other kalsarpa tools. An output schema exists, so return values need not be described, but the invocation context is largely missing.

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?

With 15 parameters and only 33% schema description coverage, the description carries a heavy burden and adds nothing: it does not explain that date/time/latitude/longitude are required birth data, nor does it hint that ayanamsa should be set to 'kp' for a KP-consistent result. The one-line text does not compensate for the coverage gap.

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 resource: the Kalasarpa dosha computed in the KP (Krishnamurti) system, including the Rahu sub-lord chain. The 'KP' qualifier plus the tool name distinguish it from the Lal Kitab (astroway_vedic_doshas_lal_kitab_kalsarpa) and Parashara (astroway_vedic_doshas_parashara_kaal_sarp) variants of the same dosha, though the description itself never states the verb 'compute/return' explicitly.

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, no statement of prerequisites (birth date/time/coordinates required), and no mention of the sibling dosha tools or the KP full-chart tool. An agent must infer from the name alone which of the several kalsarpa variants to pick.

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