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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context — the endpoint, the Vedic group, and the cost (20 credits, Tier 2) — but says nothing about output shape or what the cascade contains. With annotations carrying the safety burden, a 3 is fair.

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?

Very short and front-loaded, but the content is metadata tags (group, endpoint, cost) rather than explanatory prose. Nothing is padded, yet little of it earns its place beyond the cost line.

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 niche Vedic dasha endpoint surrounded by dozens of near-identical siblings, the description does not explain what Chara Dasha is, what the 4-level cascade returns, or how it relates to the other levels. An output schema exists so return values needn't be described, but the tool-selection context is essentially absent.

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 100% and the body schema is exhaustively documented (timezone handling, houseSystem letters, ayanamsa, target date fields), so the schema does all parameter work. The description adds nothing beyond the schema, which yields the baseline 3.

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 largely restates the title/name; its only added content is '4-level cascade', which hints at the depth of the dasha subdivision but never states a verb, what is computed, or what distinguishes it from the sibling chara_maha/antar/pratyantar/prana tools. An agent cannot tell which cascade level this is without decoding the naming convention.

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 guidance on when to use this tool versus the ~60 sibling dasha tools, including the four other Chara levels (maha, antar, pratyantar, prana). No conditions, no prerequisites, no alternatives named.

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