Doshas — Lal Kitab Pitra

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds that it outputs triggers and remedies but no details on process, dependencies, or limitations. Minimal behavioral context beyond 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?

Two sentences plus example, very concise but omits essential information. Not a model of conciseness when clarity suffers.

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 many sibling tools, the description lacks completeness. No information on output format, interpretation of triggers/remedies, or prerequisite knowledge. Severely insufficient for effective tool selection/invocation.

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 only provides an example with 5 of 11 parameters. No explanation of what each parameter means or how they affect the result. Required fields (date, time) are not described.

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 it assesses Pitri Rin (paternal-debt dosha) using Lal Kitab patterns, with triggers and remedy. This distinguishes it from other dosha tools (e.g., Parashara, KP) by specifying the Lal Kitab system.

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 over siblings like vedic_doshas_lal_kitab_full or vedic_doshas_parashara_pitru. Lacks explicit when-to-use or when-not-to-use advice.

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