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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the bar is lower. The description adds useful context beyond that: a specific cost of 20 credits (Tier 2), the endpoint, and the required parameter set. It does not discuss return values, 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 description is short and front-loads the key astrological semantics before the bracketed metadata. The bracket lines repeat some information available elsewhere, but cost and endpoint are useful and the whole is efficiently sized.

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 endpoint with a rich output schema and strong annotations, the description covers purpose and cost but omits usage guidance and parameter semantics. An agent can invoke it correctly for the required fields, but the optional parameters remain opaque beyond their schema entries.

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%, so the description needs to compensate for underspecified parameters. It does not: it merely lists the four required parameter names, adding no meaning beyond the schema's required list, and says nothing about the optional ayanamsa, timezone, houseSystem, precision, or fields parameters.

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 exact astrological quantity computed — Dig Bala, directional strength — and gives its formula (60v at preferred kendra, 0v opposite, linear gradient) plus planet-house mappings. This cleanly distinguishes it from sibling Shadbala tools such as sthana, kala, cheshta, drik, and naisargika.

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 explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named (e.g., use shadbala_full for all components). The astrological definition implies the context, but the description leaves the agent to infer selection.

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