Yogas — Jaimini Viparita Raja yoga

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

Annotations already provide readOnlyHint and idempotentHint. Description adds no behavioral details beyond source citation, meeting baseline expectations.

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 brief and front-loaded with key info (condition and source). The example request body adds bulk but is useful. Minimal waste.

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?

For an 11-parameter tool without output schema, the description lacks guidance on many inputs and output expectations. It only covers the core condition.

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 fails to explain parameters. The example request body is present but does not clarify parameter semantics or provide context beyond a sample.

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 this computes a 'Reverse Raja yoga' specifically for AK in houses 6/8/12, differentiating it from sibling tools like vedic_yogas_jaimini_raja or vedic_yogas_jaimini_dhana.

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?

It specifies the exact condition (AK in 6/8/12) and source (Sanjay Rath modern commentary), implying usage context. However, it lacks explicit when-not or alternative guidance among siblings.

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