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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description still adds genuine behavioral context: Yuddha (planetary war) is explicitly deferred and the Abda/Masa rulers are 'currently zeroed (no contribution)'. That discloses a partial/stubbed implementation, which materially affects how an agent should interpret or caveat the output.

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?

It is a single compact sentence and front-loads the main concept, but it is dense with BPHS-specific jargon and parenthetical clauses, and it is visibly truncated mid-sentence ('currently zeroed (no contribution) to…'). Efficient in length, weak in accessibility and completeness.

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 the description does convey which sub-components are computed versus deferred. But the truncation and the total absence of parameter guidance for a 15-parameter tool leave the definition short of what an agent needs to invoke it confidently.

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 is expected to compensate, but it contributes zero parameter-level meaning (no mention of date/time/latitude/longitude, ayanamsa, house system, or compact-mode fields). The high parameter count with low coverage leaves a real documentation gap that the description does nothing to close.

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 clearly identifies the resource as the Kala Bala (temporal) component of Shadbala and enumerates its constituent sub-balas (Nathonnatha, Paksha, Tribhaga, Abda/Masa/Vara/Hora, Ayana), which lets a domain-literate agent tell it apart from sibling shadbala tools. However it never states a verb or scope explicitly ('computes the Kala component for a chart'), relying on the title to supply the framing, so it stops short of a fully self-contained purpose statement.

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 mention of the sibling shadbala_* tools (full, sthana, dig, cheshta, naisargika, drik), and no indication of when to prefer this partial component over shadbala_full. Usage must be inferred entirely from the technical content.

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