vedika_varshaphal

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the Tajaka methodology, Sahams, Muntha, Tajaka yogas, sidereal zodiac, and per-call cost, but it does not state whether the operation is read-only, what permissions or rate limits apply, or what the response contains.

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 four tight sentences, front-loads the tool's identity and purpose, and includes the key differentiator and cost without wasted wording.

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 a calculation tool with no output schema, the description explains the underlying system and components but does not describe the return structure or what the resulting annual horoscope includes. It is sufficient to understand the purpose, but not fully complete for an agent needing to interpret results.

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 100%, so all six parameters are already well documented in the input schema. The description only indirectly implies year, sidereal correction, and birth data through concepts like 'each year' and 'sidereal zodiac,' adding little 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 names a specific resource (Vedic annual horoscope / Varshaphal) and explains its defining calculation: the exact moment the Sun returns to its natal sidereal position. It also distinguishes itself from the Western Solar Return sibling by noting the sidereal zodiac and Tajaka system.

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 clearly differentiates this tool from vedika_western_solar_return by stating that this uses the sidereal zodiac and Tajaka system, so an agent can route sidereal annual-return requests here. However, it does not explicitly state when to prefer this over other Vedic tools such as vedika_horoscope or vedika_panchang.

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