Yogas — Jaimini full summary

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

Annotations already indicate read-only, non-destructive, idempotent, and non-open-world behavior. The description adds 'with karaka details' but does not contradict annotations or provide significant additional behavioral context beyond what the annotations already convey.

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 succinct, consisting of two lines with a clear purpose and an example request. The example is helpful but the overall structure is minimal, though it does not waste words. A sentence about parameters would improve conciseness further.

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?

Given the complexity (11 parameters, no output schema), the description is insufficient. It does not explain what the composite output contains, how karaka details are presented, or how parameters like houseSystem, zodiacType, or ayanamsaId affect the result. The annotations cover safety but completeness is lacking.

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 and 11 parameters, the description adds no semantic meaning to any parameter. It neither lists nor explains parameters, leaving the agent without guidance on what each parameter does or how to use them effectively.

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 is a composite summary of multiple Jaimini yogas (Raja, Dhana, Daridra, Viparita) with karaka details. This directly differentiates it from sibling tools that focus on individual yoga types.

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 implies usage for a combined overview of several yogas, but does not explicitly state when to use this tool versus the individual sibling tools (e.g., vedic_yogas_jaimini_raja). No alternatives or exclusions are mentioned.

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