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

Annotations already declare readOnly/idempotent/destructive/openWorld, so the safety profile is covered. The description adds real value beyond that: the exact output contents (planet by sign with dignity state plus pakka-ghar match flag) and a YELLOW caveat that Lal Kitab is single-school with a specific K. Ashant + R.D. Mathur consensus, which is useful methodological transparency for trusting the result.

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?

Front-loaded with the key identifier and scoping rule, then the output shape, then the caveat. Two tight sentences with no padding; the Group/Cost tags are boilerplate metadata rather than description text.

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 spelled out, and the description does explain chart composition. But for a 15-parameter tool with 33% schema coverage and heavy sibling overlap, the absence of any usage or parameter guidance leaves meaningful gaps.

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 low (33%) and the description adds no parameter meaning at all. It never touches ayanamsaId, houseSystem (default P, arguably irrelevant for a fixed-house chart), zodiacType, or cosmogram, leaving several enums/blanks undocumented in both description and 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?

States a specific resource (Lal Kitab teva chart) and its defining method: fixed-house where house=sign, no ASC rotation. This technical detail differentiates it from ordinary Western/Vedic chart tools, but it never names a sibling (e.g., lal_kundali or lal_kitab_lal_kundali) that an agent should compare against when choosing.

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 statement of when to use this tool, when not to, or which alternative to prefer among the many Lal Kitab siblings (dasha, debts, kismat, life_graph). The agent is left to infer usage entirely from the chart-content description.

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