Lal Kitab Chart

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

The description is consistent with the readOnly, idempotent, and non-destructive annotations and adds context about output contents. It does not contradict annotations, though it relies on them for side-effect transparency.

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 well organized with workflow and disambiguation sections and is front-loaded with the core purpose. Minor redundancy exists between the opening paragraph and the later disambiguation note.

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?

Given the detailed input schema, output schema indication, and annotations, the description provides sufficient context for correct invocation and clear differentiation from numerous sibling tools.

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?

The input schema already provides 100% field-level descriptions with examples and defaults. The prose adds little parameter-specific meaning beyond identifying the Lal Kitab system.

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 produces the Lal Kitab house and planet schema plus Rin flags from BirthData using Lal Kitab placement rules, and explicitly distinguishes it from the natal chart and remedies tools.

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 provides explicit guidance: it is standalone for Lal Kitab queries, lists the recommended follow-up tool, and warns against confusing it with asterwise_get_natal_chart and asterwise_get_lal_kitab_remedies.

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