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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false, so the safety profile is covered. The description adds only cost information (20 credits, Tier 2), which is useful for budgeting but does not explain computation, output depth, or any dynamic behavior beyond the annotations.

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?

The description is extremely terse, consisting of a fragment plus two bracketed tags. While it is not rambling, it is under-specified for a tool with a complex input schema and dense sibling set, so the brevity reflects missing information rather than efficient conciseness.

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 and annotations cover safety, and the input schema is very detailed. However, the description omits essential context for this tool's role in a large family of dasha level tools: what Shoola Sookshma dasha is, what '4-level cascade' returns, and when to pick this level over maha, antar, pratyantar, or prana. This gap makes the definition incomplete for correct tool selection.

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 input schema itself provides extensive descriptions for birth data, timezone, fields, precision, etc. The tool description adds no parameter meaning at all, so the schema does the entire job. A baseline of 3 is appropriate when schema coverage is complete.

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 restates the title and name without a verb: 'Shoola Sookshmadasha: 4-level cascade.' It does not say what the tool computes or how it differs from sibling dasha tools such as astroway_vedic_dashas_shoola_maha, _antar, _pratyantar, or _prana. The phrase '4-level cascade' is vague and leaves the actual purpose unclear.

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 is given on when to use this tool versus any alternative. The description includes only a group tag and cost tier, with no prerequisites, context, or exclusions. An agent has no basis for choosing this over the other Shoola dasha levels.

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