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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful nuance by disclosing that the solar-return JD is approximate and that the dasha house comes from a running 35-year cycle, but it says nothing about auth, rate limits, or cost implications beyond the credit tag.

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?

Two tight sentences, with the core purpose and the returned artifacts front-loaded before the group/cost metadata tags. Nothing is padded or redundant.

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 explained, and the parameters are fully documented in the schema. The only meaningful gap is the absence of sibling differentiation against the many other Lal Kitab and Varshaphal tools, which the description leaves to the reader.

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% for the fields and precision parameters, and the body object carries a long self-description, so the baseline is 3. The description does clarify the otherwise undocumented `age` parameter by tying it to the annual progression, but that is a thin addition over what the schema already conveys.

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?

States a specific verb+resource (Lal Kitab annual progression) and the key output components (35-year-cycle dasha house, approximate solar-return JD). The 'Lal Kitab' qualifier implicitly separates it from the standard Varshaphal sibling, but the description never explicitly contrasts the two, so an agent must infer the distinction.

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 guidance. The phrase 'for full annual chart casting' hints at intent but never states when this tool should be chosen over astroway_vedic_varshaphal, astroway_vedic_lal_kitab_dasha, or the reports_lal_kitab sibling.

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