Yogas — Adhi

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

Annotations already indicate read-only and idempotent behavior. The description adds no behavioral traits beyond 'powerful for status and prosperity,' which is interpretive. No mention of output format, errors, or constraints. Minimal additional value over 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 brief and front-loaded with the definition. The example request is helpful. No superfluous content. However, it could be restructured to include parameter hints without losing conciseness.

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?

With no output schema, the description should explain what the tool returns (e.g., list of yogas, boolean, interpretation) but does not. Given 11 parameters and many sibling tools, the description is too sparse for an agent to use correctly without additional context.

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%, yet the description fails to explain any parameters beyond offering an example request body. The example only covers a subset of parameters (date, time, location), leaving 9 undocumented parameters. The description does not add meaningful semantics beyond the 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 explicitly defines Adhi Yoga as benefics in houses 6-8 from Moon, and mentions Maha Adhi Yoga. It clearly identifies the tool's function. However, it does not differentiate from sibling tools like vedic_yogas_parashara_full or vedic_yogas_parashara_dhana, so it's clear but not distinct.

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 alternatives. The description only defines the yoga, lacking any context about preferred use cases or when to avoid it.

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