Jaimini — Yogas (basic AK/DK/PK set)

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context about the specific yoga checks performed but does not disclose additional behaviors like output format or error conditions. It 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 mostly concise, covering purpose, yoga types, future roadmap, and an example in a few sentences. The inclusion of '[Group: Vedic]' and the future roadmap adds slight overhead but remains efficient.

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 11 parameters with no schema descriptions and no output schema, the description is insufficient. It fails to explain optional parameters, response structure, or how to tailor the request for different yoga results. The agent lacks crucial details for correct 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 does not explain any of the 11 parameters beyond providing an example request that only covers 5 common ones. The example omits optional fields like houseSystem, name, etc., leaving agents without guidance on their meaning or usage.

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 explicitly states 'Basic Jaimini-yoga checks based on chara karakas' and lists specific yogas (Raja, marriage, success, challenge). It clearly defines the tool's function and distinguishes it from future dedicated endpoints mentioned in the roadmap.

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 indicates this is for basic checks and notes that dedicated endpoints will be added in Phase 2, implying use this for a simpler set. However, it does not explicitly compare with sibling tools like vedic_jaimini_argala_analysis or vedic_jaimini_yogas_jaimini_*.

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