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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds the cost (20 credits, Tier 2), which is a genuinely useful behavioral signal for invocation budgeting, plus the endpoint and group tags. It says nothing further about computation semantics or limits, so it is useful 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?

Extremely compact and front-loaded: the level/cascade statement comes first, then the metadata tags. Every element carries information and there is no padding. The bracketed Group/Endpoint/Cost lines are metadata rather than prose, which slightly dilutes the description proper.

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 values need not be explained, but this tool lives in a dense family of identical-looking dasha endpoints where routing is the hard part, and the description does nothing to resolve that ambiguity. For a Tier-2, 20-credit call the definition gives no selection criteria, which is a real gap.

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 itself is exhaustively documented (coordinate forms, timezone vs timezoneOffset precedence, houseSystem letters, ayanamsa rules). The description contributes no parameter meaning beyond that, so the baseline 3 for fully covered schemas is correct.

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 resource and scope: 'Ashtottari Pratyantardasha: 3-level cascade (MD → AD → 8 PDs)', which tells the agent both the dasha system and the exact depth of the level being computed. The naming and the '8 PDs' detail distinguish it from the maha/antar/prana/sookshma siblings in the same family. It stops short of explicitly naming those siblings, so it is clear but not fully self-routing.

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 and no exclusions. With ~70 near-identical dasha siblings (ashtottari_antar, ashtottari_prana, ashtottari_sookshma, plus every other system at every level), the description never says which level to pick or what input conditions select this tool. The cascade notation implies what is produced but gives no decision guidance.

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