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 fully covered. The description adds useful context by naming what comes back (running 35-year-cycle dasha house plus approximate solar-return JD) and the credit tier, but says nothing about auth, rate limits, or failure modes.

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?

One front-loaded sentence carries the substance, followed by short structured metadata lines (group, endpoint, cost). No filler, no repetition of schema content; only the boilerplate block borders on non-essential.

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, rich annotations, and a fully documented input schema, the definition only needs to frame purpose and selection — which it mostly does. The lone gap is the absence of any signal distinguishing it from the other Lal Kitab and Varshaphal siblings.

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%, so the baseline is 3. The description does single out `age` as the pivot for the annual progression, which maps meaning to the one non-generic parameter, but adds no range, default, or edge-case semantics beyond the schema.

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?

"Lal Kitab annual progression at given `age`" gives a clear verb+resource and the annual-scoping is specific enough to separate it from the general Lal Kitab dasha tools. It never names a sibling, though, so an agent weighing it against astroway_vedic_lal_kitab_dasha or astroway_vedic_varshaphal must infer the distinction from the label alone.

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?

The phrase "for full annual chart casting" gestures at the use case, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent gets an implied context rather than a routing rule.

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