divine_get_varshphal_panchadhikari

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so safety is covered. The description adds no behavioral detail beyond that, such as what the Panchadhikari output represents, whether it requires special interpretation, or any call-specific caveats.

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 a single concise sentence with no wasted words and gets straight to the point. It earns a high score for structure, though it could have used the space to add missing domain context.

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 a rich schema, output schema, and safe-read annotations, the mechanical calling context is covered. However, the description fails to explain what 'Panchadhikari' is or when to choose this tool among dozens of varshphal-related siblings, leaving a significant contextual gap for correct tool selection.

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 the parameters varshphal_year and the nested KundliInput are fully documented. The description adds no new parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the verb 'Get' and names the specific resource 'Varshphal Panchadhikari', but the parenthetical '(annual chart)' is ambiguous and doesn't clarify what Panchadhikari means or how it differs from sibling tools like divine_get_varshphal_horoscope_chart or divine_get_varshphal_muntha. It is not a tautology, but purpose clarity is limited by unexplained domain jargon.

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 is provided about when to use this tool versus the many varshphal siblings, and no alternative tools or exclusions are mentioned. The description only restates the call context ('given year and birth data') without helping an agent select among the large family of related tools.

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