divine_get_varshphal_horoscope_chart

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds the output type ('SVG') and the annual-year scoping, which are useful behavioral details beyond the annotations. No contradiction exists.

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?

A single, front-loaded sentence that captures everything essential with no redundant words. Every clause adds information: annual chart, divisional range, SVG output, year.

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?

All required inputs are specified in the schema, an output schema exists, and the description conveys the core purpose and output format. The agent has everything needed to call this tool correctly.

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 parameters are fully documented. The description mentions 'D1..D60' and 'given year', but these merely mirror the schema's chart_id and varshphal_year descriptions. No new semantics are added.

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 verb ('Get'), a clear resource ('Varshphal annual divisional horoscope chart'), the range of charts ('D1..D60'), the output format ('as SVG'), and the scope ('for the given year'). This distinguishes it from generic horoscope chart tools and other varshphal calculation tools.

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?

The purpose statement makes the context obvious: use this when you need the annual (Varshphal) divisional chart as an SVG. It does not explicitly list alternatives or exclusions, but the tool name plus description provide a clear semantic niche among the many sibling tools.

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