Yogas — Dhana (wealth)

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds group (Vedic), cost (50 credits), and example request, but no further behavioral traits like side effects or limitations beyond what annotations cover. Adequate but not additive.

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 sentences defining the yoga plus group/cost info and an example. Concise and front-loaded with key concept. The example is somewhat lengthy but not excessive. No wasted sentences.

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?

Missing return format, output schema, prerequisite conditions (e.g., need accurate birth data), and how to interpret results. With 11 params and no output schema, agents lack sufficient context for correct invocation and result handling.

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 (2 required), the description provides no parameter explanations. The example request body shows typical values but does not explain the meaning or usage of any parameter. Fails to add value beyond the input schema.

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 defines Dhana Yoga as the connection between lords of wealth houses (1,2,5,9,11) via conjunction, mutual drishti, or strict parivartana. This is specific and differentiates from other yoga tools like raja yogas or jaimini dhana yogas, as it specifies Parashara method.

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 explicit guidance on when to use this tool vs alternatives such as vedic_yogas_jaimini_dhana or other yogas. Lacks context for selection, no when-not-to-use or prerequisites mentioned.

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