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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered and the description does not contradict it. The description adds interpretive context (karma 'unilluminated', remedies essential) and discloses the cost tier (20 credits, Tier 2), which is genuinely useful non-schema information, but says nothing about what is returned or response shape — mitigated by the existing output schema.

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?

Two compact sentences plus two metadata tags; the technical definition is front-loaded and nothing is padded. It is arguably slightly under-written for a 15-parameter tool, but there is no wasted prose.

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 explained, and annotations cover the safety profile. What remains missing is guidance on when to use this versus the adjacent lal_kitab concept tools, and any coverage of the many undocumented parameters — a real gap given 33% schema coverage and 15 inputs.

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 only 33% across 15 parameters, so the description is expected to compensate and does not — it offers zero parameter guidance. Several parameters (city, name, cosmogram, zodiacType, houseSystem) carry no schema description at all, and the description leaves them entirely undefined.

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 precisely defines the computed artifact — houses with no planet and no Parashari aspect — which is a narrow, distinctive resource among the many lal_kitab siblings (sleeping_house, debts, kismat, prosperity, remedies). The action verb ('compute/return') is never stated explicitly, but the resource definition is unambiguous enough for an agent to select it correctly.

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 when-to-use guidance and no alternatives named. There is no statement distinguishing this from the sibling astroway_vedic_lal_kitab_sleeping_house (a related but distinct Lal Kitab concept) or from astroway_vedic_lal_kitab_remedies, which the description's closing clause ('remedies are essential') could easily be confused with. Usage is only implied by the domain term.

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