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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful operational context not in the annotations: the HTTP endpoint and the cost (20 credits, Tier 2). It does not explain what a 'cascade' returns or how the five levels nest, which is the main behavioral unknown.

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 tight and front-loaded: purpose first, then group, endpoint and cost in bracketed metadata that an agent can parse quickly. It errs toward under-specification rather than verbosity, but nothing present is wasted.

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. Still, for a 3-parameter paid dasha endpoint inside a family of five near-identical siblings, the description leaves the agent without usage guidance or level-selection logic, 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%, with the body/natal-chart object, fields and precision all documented in the schema itself (including the timezone, lat/lon and houseSystem caveats). The description contributes nothing further about parameters, so the baseline 3 for schema-carried semantics is appropriate.

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 the specific dasha system and level ('Shoola Pranadasha') and adds the scope qualifier '5-level cascade (finest grain)', which helps position it against the shoola_maha/antar/pratyantar/sookshma siblings. However, it is a bare noun phrase with no verb, so the agent must infer that it computes/returns periods rather than, say, lists definitions.

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 guidance, no prerequisites (e.g. that birth data with date/time/coordinates is required), and no explicit routing against the four other Shoola levels. 'Finest grain' implies a timing-resolution intent but never states the condition that should select this tool over shoola_sookshma or shoola_maha.

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