Lal Kitab — Kismat (fortune indicator)

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

Annotations declare readOnlyHint=true, so no side effects. The description provides insight into the scoring logic (how fortune is calculated) but does not describe the output structure or any other behavioral details. Adds some value beyond annotations but incomplete.

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?

Description is short and includes an example, but the structure could be improved. It lacks clear separation between purpose, scoring, and example. Acceptable conciseness but at cost of completeness.

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?

With 11 parameters, no output schema, and no description of return values, the description is severely incomplete. It does not enable an agent to understand what the tool returns or how to set parameters beyond the example.

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 0%, and the description does not explain any of the 11 parameters. The example request body shows values but no semantics. Without parameter guidance, the tool is hard to use correctly.

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?

Description indicates it computes a 'fortune score' using Lal Kitab rules (pakka ghar, own sign, exalted, debilitated) and cites a reference, but does not explicitly state the overall function or distinguish from other vedic_lal_kitab_* tools. Purpose is implicit rather than clear and specific.

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 use this tool versus alternatives. The description lacks any context about appropriate use cases, prerequisites, or comparisons to sibling tools.

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