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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the output shape (bindus per planet/sign and total), which is genuine behavioral context, but says nothing about ayanamsa-dependence, required birth data, or cost implications beyond the bracketed tag.

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?

Effectively a single front-loaded sentence that puts the technique name and output first, with group and cost as compact bracketed metadata. No wasted prose, though the metadata lines add little to selection.

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?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. However, for a 15-parameter tool with 33% parameter description coverage, the description is thin on how astrological settings (ayanamsa, zodiacType, houseSystem) affect the result.

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?

None of the 15 parameters are illuminated by the description, and schema coverage is only 33%. Several parameters (cosmogram, zodiacType, houseSystem, ayanamsaId) have no description text, so the description does not compensate for the coverage gap even though the core date/time/lat/lon params are self-evident.

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 a specific verb and resource ("Calculate the Ashtakavarga benefic point table for a Vedic chart") and even enumerates the outputs (individual bindus per planet per sign plus Sarvashtakavarga). This clearly separates it from generic Vedic siblings like shadbala or bhavabala. It stops just short of explicitly naming a sibling it replaces or being confused with.

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 guidance, no prerequisites, and no mention of alternatives among the many Vedic analysis tools. An agent must infer that this is a Vedic strength/point-scoring technique from the phrase "for a Vedic chart" alone.

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