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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real substance by naming the BPHS rule set (A.27.10-19), the varga set, and the weighting scheme, plus the cost tier. It does not, however, disclose response shape or that the result is deterministic per chart, which the annotations already imply.

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 dense sentence for the concept plus a bracketed metadata block, with the core definition front-loaded. The parenthetical component list is information-rich rather than filler, though it could be trimmed for an agent that only needs selection cues.

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 explained, and annotations cover the safety profile. What is missing is when to prefer this over the other shadbala endpoints and any hint at the 15 mostly-undocumented parameters, leaving the definition adequate but incomplete for a Tier-2 paid calculation.

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, and the description says nothing about any parameter — not the ayanamsa selection, the timezone/timezoneOffset interplay, the fields compact mode, or the four required inputs. With low coverage the description is expected to compensate and does not.

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 the exact quantity computed ('Sthana Bala, the sum of 5 sub-strengths') and enumerates the five components, which distinguishes it from sibling shadbala sub-tools (dig, kala, cheshta, drik, naisargika) and from shadbala_full. It never states in plain terms that it returns positional strength values, but a competent agent can infer the output.

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 statement of when to use this tool rather than astroway_vedic_shadbala_full or the other shadbala sub-tools, and no prerequisites or context beyond the required-input line. The agent must infer routing from the name alone.

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