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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context in the form of the weighting scheme and the direction of the scale ('higher = more fortunate'), but says nothing about what inputs are required, cost implications beyond the credit tag, or determinism of the score.

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?

Terse and front-loaded: the scoring rubric leads, followed by the source citation and two bracketed metadata tags. No filler sentences, though the formula, while informative, is dense and the description could be clearer about the action it performs.

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 no explanation, and the description does convey the scoring semantics. But for a 15-parameter computation tool it omits any usage context, input expectations, or routing relative to the dense Lal Kitab sibling set, leaving clear gaps.

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 schema does not fully document its inputs, and the description compensates for none of them — it mentions no parameter at all. Even the four required parameters (date, time, latitude, longitude) are left to the schema with no interpretive guidance.

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?

States a specific resource (Lal Kitab kismat/fortune) and even the exact scoring rubric (+2 pakka ghar, +1 own sign, +2 exalted, −2 debilitated), which lets an agent understand what the tool computes. However the verb is left implicit — it never plainly says 'computes a fortune score from a natal chart' — and it does not differentiate itself from near siblings like vedic_lal_kitab_prosperity or _life_graph.

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 on when to choose this over the many sibling tools (prosperity, life_graph, lal_kundali, dasha, etc.), and no prerequisites stated. The agent is left to infer usage entirely from the name and the scoring formula.

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