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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered. The description adds the Lal Kitab computational rule and the credit cost (20 credits, Tier 2), which is useful context, but says nothing about return shape, latency, or error behavior for the requested chart.

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?

Roughly two lines, front-loaded with the authoritative rule before the metadata tags. Nothing is wasted, though the [Group]/[Cost] tags sit in the same block a reader scans for usage guidance.

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, 4-required tool with low schema description coverage, the description omits everything an agent needs to invoke it correctly beyond the domain concept. An output schema exists, so return values need not be explained, but input selection (ayanamsa, house system, timezone vs offset) is left 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?

With 15 parameters and only 33% schema description coverage, the description carries a compensation burden it does not meet: it mentions no parameter at all, not even which four are required or how date/time/lat/long interact. The schema does define enums and some descriptions, but the two aliased ayanamsa fields and the zodiac/house-system choice are left entirely to the caller.

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?

States a specific verb+resource: computes Manglik dosha under the Lal Kitab school, and even gives the operative rule (Mars in 1/4/7/8/12 with LK cancellations). An agent can distinguish it from the KP and Parashara manglik siblings by the named school, though the description never explicitly names those alternatives.

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 statement of when to choose this tool over astroway_vedic_doshas_kp_manglik, astroway_vedic_doshas_parashara_mangal, or astroway_vedic_compatibility_manglik_check, and no prerequisites beyond the implicit birth data. The only routing cue is the school name embedded in the purpose sentence.

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