Lal Kitab — Sukh (prosperity yoga)

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

Annotations indicate readOnlyHint=true, idempotentHint=true. Description adds that it counts benefics with fixed +2 each, consistent with idempotent read operation. However, it does not disclose additional behavioral traits beyond what annotations already cover, so only moderate value.

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 extremely concise with only two sentences: one functional description and one example. All words are necessary and the example is immediately helpful. No fluff.

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 11 parameters and no output schema, the description lacks completeness. It does not describe the return format, error handling, or default values for parameters like houseSystem and ayanamsaId. The tool assumes knowledge of Lal Kitab without further explanation.

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 0%, meaning no parameter descriptions in the schema. The description provides an example request body with typical birth data parameters but does not explain the meaning or constraints of each parameter. The example helps but is insufficient to convey complete parameter semantics.

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 calculates a sum of benefic planets (Moon, Mercury, Venus, Jupiter) in specific houses (2,5,9,11) for Lal Kitab prosperity yoga. It uses specific terminology (LK dhana yoga sum) and distinguishes from siblings by specifying LK fixed houses.

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 explicit guidance on when to use this tool versus alternatives. The description implies it's for Lal Kitab prosperity yoga calculation but does not mention when not to use it or provide comparisons with sibling tools like vedic_lal_kitab_dasha or vedic_lal_kitab_debts.

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