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

No annotations are provided, so the description carries the full burden. It usefully discloses that BAV and SAV are combined into a single response and that birth time is mandatory, but it says nothing about computation cost, permissions, or how failures are surfaced beyond what the schema already notes. Adequate but thin for a no-annotation tool.

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?

Two tightly packed sentences that front-load what is produced and then the key prerequisite. No filler, though the line about lagna as 'one of the eight sources' is terse to the point of being cryptic without domain knowledge.

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. But for an 8-parameter tool with 25% schema coverage and no annotations, the description omits parameter guidance and error handling that an agent would need. It covers the essentials (what it computes, birth time needed) and little more.

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 25% across 8 parameters, and the description does not compensate: it does not explain ayanamsa choices, lang, place, or utc_offset. Only the birth-time requirement is hinted at, and the informative notes (chart_id conflict, time_ambiguous) live in the schema, not the description.

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 computation: Ashtakavarga (Parashari) bindus across 12 signs for seven grahas (BAV) plus the consolidated SAV, returned in one response. An agent can tell this apart from generic chart tools like natal_chart or varga_chart. It stops short of explicitly naming a sibling to prefer over it, but the domain term is precise.

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?

It states a prerequisite (birth time is required, with lagna as one of the eight sources), which implies when the tool is applicable. However, there is no explicit when-to-use versus alternatives such as varga_chart, nor any exclusion guidance. Usage is inferred rather than directed.

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