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

Annotations already declare the full safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description's burden is light. It adds two non-annotation facts that matter for selection: the [Vedic] family grouping and the 20-credit Tier-2 cost. It says nothing about input expectations (birth data) or whether the chart is computed for a single moment.

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 short lines that are front-loaded with the subject, so an agent gets the purpose in the first clause. The bracketed cost/group metadata is slightly toy-like but genuinely useful for routing, and there is no padding or repetition.

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 tool in a family of fifteen near-identical varga siblings, the description omits everything that would make this tool callable with confidence: input expectations, choosing among varga divisions, and the relationship to the generic divisional endpoint. The existence of an output schema excuses it from explaining return values, but not from the selection and parameter gaps.

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 33%, below the 50% threshold, so the description must compensate for undocumented parameters and does not. Fifteen parameters are present (city, date, time, name, houseSystem, zodiacType, ayanamsaId, cosmogram, etc.) and the description explains none of them; it does not even clarify that city/date/time/latitude/longitude are the birth-data inputs.

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?

Names a specific chart (Akshavedamsa/D45) and gives its traditional signification (general life patterns, paternal lineage), which is more than a tautology. However, it never states the action (compute/cast a divisional chart) and gives no differentiation from the fourteen sibling varga tools (D1, D2, D3, D9, D60, and notably astroway_specialized_vedic_divisional). An agent can only tell them apart by decoding the D-number from the tool name.

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 prerequisites, and no named alternative. The only selector offered is the credit cost line, which tells the agent the price but not the condition under which this chart is the right choice versus another varga or a full kundli.

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