Panchang — Yoga

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

Annotations already declare idempotentHint=true, readOnlyHint=true, destructiveHint=false. The description does not contradict and adds the calculation formula, but does not discuss edge cases, required permissions, or error behavior. With annotations covering the safety profile, a 3 is appropriate.

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 very short (two lines plus example). It is not bloated, but it could include a brief explanation of the output and key parameters without becoming lengthy. The example is helpful but not front-loaded.

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, no output schema, and 0% schema coverage, the description is severely incomplete. It does not describe the result format, parameter dependencies, or how the calculation works with different zodiac/ayanamsa settings. The example only covers a subset of inputs.

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%, so the description must compensate. It provides an example with 5 of 11 parameters but does not explain the meaning of any parameter (e.g., houseSystem, zodiacType, ayanamsaId, cosmogram). Many parameters are directly relevant to the calculation but are left undocumented. The formula hint is not enough.

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 states it computes 'Surya-Chandra Yoga (1-27)' with a formula, which gives a specific name. However, it does not clarify what the output represents (e.g., a yoga number or name) or distinguish it from sibling tools like vedic_panchang_full or vedic_panchang_tithi. The purpose is somewhat clear but not specific enough to differentiate within the group.

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 vs alternatives. Sibling tools include many vedic_panchang_* functions for specific calendar elements, but the description does not mention when to pick this yoga calculator over others. The 'Group: Vedic' and cost note are not usage guidelines.

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