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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful non-annotation context: the cost (20 credits, Tier 2) and the equivalence caveat against the debt endpoint. Auth requirements and rate-limit behavior are not addressed, but the cost disclosure is real added value.

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 with the purpose sentence, then a compact bracketed metadata block for group, endpoint, required params and cost. No filler, and the most decision-relevant facts come first. The endpoint path is slightly redundant but costs little.

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 structure need not be explained. Required inputs, cost, engine equivalence and the six debt types are all present, and annotations cover safety. Missing only a note on what the "active count" means or auth/prerequisite conditions, which is minor for a read-only chart tool.

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?

The [Required: date, time, latitude, longitude] line only restates the schema's required array, adding no new meaning. There are 10 undocumented parameters, but the genuinely tricky ones (timezone, timezoneOffset, fields, precision, ayanamsa) do carry schema descriptions, so the effective gap left to the description is modest.

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 ("Aggregate") and resource (all 6 Rin ancestral debts), enumerating the six types, and explicitly distinguishes itself from the sibling astroway_vedic_lal_kitab_debts by noting it is the same engine "but framed as dosha." An agent can separate it from the debt tool without opening either schema.

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?

The "same engine as /lal-kitab/debts but framed as dosha" clause gives clear context for choosing between the two near-identical tools, and the required-parameter line signals the inputs needed. It stops short of an explicit when-to-use/when-not rule, but the framing cue is sufficient to route correctly.

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