Yogas — Jaimini Dhana yoga

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

Annotations already indicate read-only and idempotent behavior. The description adds the specific astrological condition for the yoga, which is useful but does not elaborate further on behavior 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?

Two concise sentences plus an example. No redundant or filler content.

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?

Lacks output schema and details about what the returned data contains. For a specialized vedic yoga calculation, the description is too sparse to fully inform an agent about the tool's capabilities.

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 coverage and 11 parameters, the description provides no parameter explanations. The example request body is insufficient for understanding parameter meaning or required formats.

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 the tool computes Jaimini Dhana yoga, specifying the condition (AK or AmK in 2nd/11th from lagna) and the outcome (wealth indicator). It is distinct from sibling tools like vedic_yogas_jaimini_daridra or vedic_yogas_jaimini_raja.

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 guidance on when to use this tool versus other yoga tools (e.g., raja, daridra). The description only provides a generic example request body, failing to clarify context or alternatives.

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