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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description's one genuine addition is the cost disclosure (20 credits, Tier 2), which the annotations do not carry and which is useful for an agent budgeting calls. It says nothing about computation behaviour, determinism across ayanamsa choices, or latency.

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?

Extremely short and front-loaded: purpose first, then two bracketed metadata tags. Nothing is wasted, but the brevity tips into under-specification for a 15-parameter computation tool rather than genuine concision.

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 described, and annotations carry the safety profile. However, for a 15-parameter tool the description leaves critical omissions: no statement that date/time/latitude/longitude are the birth-data inputs, no mention that ayanamsa/zodiacType materially change the result, and no routing guidance among the many varga and divisional-chart siblings.

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?

Fifteen parameters with only ~33% schema description coverage, and the description contributes nothing about any of them. The well-documented schema fields (fields, ayanamsa, timezone, precision, timezoneOffset) are documented by the schema, not the description, while city, name, cosmogram, ayanamsaId, zodiacType and houseSystem are undocumented in both places — a gap the description should have helped 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?

States the resource precisely — the Shodasamsa (D16) divisional chart — and adds its traditional significations (vehicles, comforts, conveyances), which meaningfully separates it from the other varga siblings such as D10 (career) or D9 (dharma). It never explicitly says it computes the chart from the supplied birth data, but the verb is implicit and the sibling naming pattern makes it inferable.

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 gives no when-to-use guidance, no prerequisites, and never names an alternative (e.g. when to pick D16 over D1/D9 or the generic astroway_specialized_vedic_divisional tool). The only supplementary text is grouping and billing metadata, which is not usage guidance.

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