Jaimini — Graha Drishti (planet aspects)

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the specific aspect rules for each planet, but this primarily describes output content rather than behavioral traits like side effects or prerequisites. The description does not contradict 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 with two sentences and an example, placing critical information (rules, context) upfront. The example could be shortened, but overall it is well-structured and avoids unnecessary detail.

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?

The tool has 11 parameters, no output schema, and no parameter descriptions. The description only covers the core computation and an example, failing to explain the purpose of many parameters (e.g., city, name, cosmogram) or the structure of the response. This leaves significant gaps for effective agent usage.

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?

With 0% schema description coverage, the description must compensate by explaining parameters beyond the example request body. It only illustrates date/time/timezone/lat/lon via example, leaving 8 parameters (e.g., houseSystem, zodiacType, ayanamsaId) unexplained. This is insufficient for an agent to understand how to use all inputs.

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 computes per-planet graha drishti using specific Parashari rules (e.g., Mars 4/7/8, Jupiter 5/7/9), distinguishing it from the sibling tool vedic_jaimini_drishti_rasi (rasi drishti) by explicitly mentioning it is used alongside rasi drishti in Jaimini-context dashboards.

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?

The description specifies that the tool is 'used in Jaimini-context dashboards alongside rasi drishti,' indicating when it is appropriate to use. However, it does not explicitly state when not to use it or provide alternative tools for different contexts.

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