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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new facts: the cost (20 credits, Tier 2) and the cascade depth. It stops there, disclosing nothing about volume of output or how the four levels nest.

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 short and front-loaded, with no wasted wording. It is terse rather than bloated; the brevity is efficient, even if the content itself is thin.

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?

Given an output schema and full annotations, the return format does not need explaining, but the one thing an agent needs in a catalog of dozens of dasha tools — how sookshma differs from antar/pratyantar/prana/maha — is absent. For a specialized Vedic endpoint this leaves a real selection 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 coverage is 100% and the nested body schema carries a very detailed description of birth data, timezone handling, and compact-mode fields. The description adds nothing beyond the schema, so the baseline 3 applies.

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 names the resource (Shodashottari Sookshmadasha) and adds a structural clue ('4-level cascade'), but it never explains what distinguishes sookshma from the sibling levels antar, pratyantar, prana, and maha that sit right next to it in the tool list. An agent must already know the dasha taxonomy to know when this level applies.

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, no prerequisites, and no reference to any alternative. The only non-definitional content is group and cost metadata, not selection guidance.

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