Lal Kitab — Blind houses (Andha bhava)

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

Annotations declare readOnlyHint=true, idempotentHint=true, etc., and the description adds context about the meaning of blind houses (karma unilluminated, remedies essential). However, it does not describe output format or any side effects beyond annotations. No contradiction with annotations.

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 concise, two sentences plus a group note and example. It front-loads the key concept. However, the example is somewhat redundant with the schema and could be replaced with parameter guidance.

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 specialized Lal Kitab tool, the description defines blind houses but lacks information on output content, interpretation, or prerequisites. The absence of an output schema further reduces completeness. The tool would be hard to use without additional context.

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?

With 11 parameters and 0% schema description coverage, the description adds no parameter information. The example request body is provided but does not explain parameters beyond what the schema already shows. The description fails to compensate for the lack of schema descriptions.

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 defines what a blind house is in Lal Kitab terminology, specifying conditions (no planet, no Parashari aspect). However, it does not differentiate from sibling tools like vedic_lal_kitab_sleeping_house or vedic_lal_kitab_planet_house_effect, so the uniqueness is implied but not explicit.

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 guidance is provided on when to use this tool versus other Lal Kitab tools. The description lacks any when-to-use or when-not-to-use context, making it difficult for an agent to select it among many siblings.

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