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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds genuinely new behavior: the cost (20 credits, Tier 2), the group, and the HTTP endpoint. It still does not disclose auth requirements, rate limits, or the cost of failure, so it is useful but not rich.

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?

Three short sentences, front-loaded with the most distinguishing fact (5th-level, finest grain), followed by compact bracketed metadata. No sentence is wasted, though the '[Group/Endpoint/Cost]' tags are boilerplate rather than explanation.

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 no explanation, and the schema is thorough on inputs. What is missing for a 3-parameter analytical endpoint in a family of ~60 near-identical dasha siblings is any routing context (when to pick prana over sookshma or pratyantar) and any hint that birth data plus an optional target date/time drive the calculation.

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 birth-data schema plus its embedded description already document date/time/latitude/longitude, timezone semantics, houseSystem, and the compact-mode fields/precision parameters. The tool description adds nothing beyond that, which is the correct baseline of 3 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?

The description names the specific technique (Vimshottari Pranadasha), places it precisely in the dasha hierarchy ('5th-level Dasha, the finest grain', '5-level cascade'), and states the resulting period size. That differentiates it from its many vimshottari siblings (maha/antar/pratyantar/sookshma). It never states an explicit verb or that it computes the dasha from birth data, so it stops just short of a 5.

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 or when-not-to-use guidance and no sibling is named as an alternative. 'Finest grain' plus the few-hours-to-few-days duration implicitly signals that this is for very narrow timing questions, but the agent must infer that and infer that coarser levels exist as options.

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