Jaimini — Rasi Drishti (sign aspects)

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) cover safety. The description adds the computational rule and source (Jaimini Sutras 1.1), but does not disclose return format, pagination, or error behavior. It provides modest added 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?

The description is concise at three lines plus an example, with a clear structure: rule, reference, group, sample. It front-loads the core purpose. However, it could be improved by including parameter explanations without becoming overly long.

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?

Despite annotations covering safety, the description lacks essential context: no output format, no parameter explanations, and no usage notes. For a tool with 11 parameters and no schema descriptions, this is insufficient to fully specify its behavior.

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%. The description does not explain any of the 11 parameters (e.g., houseSystem, zodiacType, ayanamsaId, cosmogram) beyond a sample request. Agents cannot learn parameter meaning from the description, relying entirely on parameter names and schema, which is insufficient.

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 that this tool computes a 'Jaimini rasi drishti table' for sign aspects, specifying the exact rule for movable, fixed, and dual signs. It is distinct from sibling tools like vedic_jaimini_drishti_graha (planetary aspects) and vedic_jaimini_argala_analysis, making its purpose unambiguous.

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 explicit guidance is provided on when to use this tool versus alternatives. With many vedic_jaimini_* siblings, agents are left to infer usage context without direction on when sign aspects are needed over other Jaimini calculations.

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