divine_get_lal_kitab_debts

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds context by specifying the output: 'karmic debts identified in the chart per Lal Kitab, such as self, mother, relative or unborn debts.' This goes beyond the annotations by describing the nature of results.

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?

The description is two sentences, front-loaded with the core purpose, and efficiently states what the tool returns. No filler or redundancy.

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?

For a tool requiring a rich KundliInput with many fields, the description provides minimal context. However, an output schema exists, so return format isn't needed. The description does not mention input requirements beyond 'birth chart,' though the nested schema has detailed field descriptions. It is adequate but not thorough.

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 0% for the top-level 'params' parameter, and the description does not mention any input requirements or fields. It only says 'for a birth chart,' which is too vague. Since the schema coverage is low, the description should compensate by explaining parameters (e.g., needing full birth details, timezone, etc.), but it does not.

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 clearly states the tool retrieves 'Lal Kitab debts (rin) for a birth chart,' with a specific verb (get), resource (debts), and domain (Lal Kitab). It also lists example debt types, distinguishing it from sibling tools like planetary positions or dasha analysis.

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 description implies when to use it (when karmic debts are needed) but provides no explicit exclusions or comparisons to alternatives. It doesn't say 'use this instead of X' or note prerequisites like needing a full birth chart.

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