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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds value by indicating it returns multiple advanced calculation types (BAV, SAV, Reduced Ashtakavarga, Shodhya Pinda) and cites scriptural chapters (Ch. 67-68, 69), which helps the agent understand the scope. However, it does not mention pagination, rate limits, or data volume; with no output schema, the agent is left guessing about the response structure. The description adds some but not rich behavioral context beyond annotations.

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 two sentences long with one additional keyword line. The first sentence clearly states the tool's purpose and outputs; the second lists use cases. The trailing keyword string is slightly redundant but does not harm. It is front-loaded and effective, though the third line could be omitted without loss. A score of 4 reflects near-ideal conciseness.

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?

Given the tool's high complexity (8 parameters, 4 required, detailed Vedic calculations) and no output schema, the description covers the main purpose, outputs, use cases, and scriptural basis. It does not describe the exact structure of return values, which would help an agent parse the result. However, with 100% schema coverage and clear annotations, the description is sufficiently complete for an agent to select and invoke the tool.

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 100% (all 8 parameters documented in the schema), so baseline is 3. The description, however, does not add any additional parameter guidance. It neither explains the parameters nor clarifies how they relate to Ashtakavarga calculations. Given the high schema coverage, the description's lack of param info is acceptable but not exceptional. Score 4 reflects that the schema already serves well, but the description could still add value.

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 explicitly names the tool as calculating 'complete Ashtakavarga analysis per Brihat Parashara Hora Shastra (BPHS)' and lists specific outputs (Bhinnashtakavarga, Sarvashtakavarga, Reduced Ashtakavarga, Shodhya Pinda). It distinguishes from siblings by focusing on Ashtakavarga alone, unlike many other post tools for aspects, dashas, or divisional charts.

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?

The description states this is 'essential for transit prediction timing, house strength analysis, dasha result evaluation, and planetary strength comparison', giving clear contexts. However, it does not explicitly say when NOT to use it or mention alternatives among the 50+ sibling tools, such as shadbala for strength or transit for predictions—guidance on exclusions is missing.

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