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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds the credit cost (20 credits, Tier 2) and group tag, which is useful billing context, but says nothing about output shape, what 'running MD' means when targetDate falls outside any period, or any rate/limit behavior.

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?

Roughly two lines, front-loaded with the operation and its two key inputs, with zero filler. It is efficient, though the metadata tags (Group, Cost) consume a meaningful share of an already very short string.

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?

With an output schema present and annotations covering the safety profile, the description need not explain return values. However, for a specialized Jyotish dasha tool surrounded by hundreds of siblings, it omits the domain concept (what an antardasha is, how it relates to pratyantar/prana) and the meaning of the required seed option, leaving the agent without enough to route confidently.

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%, so the schema already documents the birth-data block, fields, and precision. The description adds only a little: it ties targetDate to the period being resolved and labels antardasaSeedOption as a seed choice, but never explains what values 1/2/3 mean or what houseIndex and targetTime do.

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 states a specific verb+resource: it computes Shoola Antardasha sub-periods of the running mahadasha at targetDate. This is clear within the Vedic dasha family, but it does not explicitly distinguish itself from the adjacent shoola_pratyantar, shoola_prana, or shoola_sookshma siblings that also return nested sub-periods.

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 when-to-use context is given, no alternatives are named, and no prerequisites are stated. The only hint is 'per chosen antardasaSeedOption', which implies a choice but never explains when to pick option 1, 2, or 3 or why one would call this instead of a sibling dashas tool.

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