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 operational facts — the POST endpoint and a 20-credit Tier 2 cost — but says nothing about output shape, latency, or pagination/limits on the cascade depth.

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: the subject comes first, followed by bracketed metadata lines. There is no filler, though '4-level cascade' is too compressed to carry real meaning.

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 described, and annotations cover safety. But for a tool with a required multi-field birth-data body sitting among ~10 near-identical Ashtottari and other dasha-level siblings, the description supplies no disambiguation, no usage context, and no explanation of what the sookshma cascade yields.

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 nested birth-data object, fields, and precision parameters are thoroughly documented in the schema itself. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

Names a specific dasha system and level (Ashtottari Sookshmadasha) and hints at depth with '4-level cascade'. However, it never explains what a sookshma-level dasha is or how it differs from the many sibling levels (maha, antar, pratyantar, prana), so an agent must infer the distinction from the name alone.

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?

No guidance on when to request this depth versus ashtottari_maha/antar/pratyantar/prana, and no prerequisites or exclusions. The metadata lines give group/endpoint/cost but nothing about selection context.

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