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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful non-annotation context: the endpoint, the 20-credit Tier 2 cost, and the sensitivity of the result to birth-time precision. Return format is not described, but an output schema 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?

The lead sentence conveys the chart's identity and accuracy caveat first, followed by a compact structured metadata block. Nothing is padded, though the bracketed endpoint/required list is largely machine-facing rather than agent-facing.

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 15-parameter chart tool with an output schema and full annotation coverage, the description supplies what is needed to call it (required inputs, cost, precision caveat). However it offers no differentiation from the ~16 sibling varga tools, so an agent lacks the cues to select D60 correctly rather than D9 or D10.

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 only 33% across 15 parameters, so the description should compensate but does not. It merely restates the four required parameters (date, time, latitude, longitude) with no added meaning, leaving the behavior of optional parameters such as zodiacType, houseSystem and ayanamsaIdId undocumented.

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 (the Shashtiamsa / D60 divisional chart) and its astrological meaning, which distinguishes it from the many other varga siblings by divisional number. It does not use an explicit action verb or name a sibling, but the resource is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative varga tool is named. The lone caveat ('high precision needed in birth time') is an accuracy warning about the input, not a usage condition for choosing this tool over d9, d10, etc.

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