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

Annotations already declare readOnlyHint/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the endpoint (POST /v1/vedic/varga/D10), the required input set, and a cost of 20 credits (Tier 2), which no annotation conveys. It says nothing about payload size, latency, or ayanamsa-sensitive behavior, so a 3 is fair.

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 compact and front-loaded: purpose first, then bracketed metadata blocks for group, endpoint, required params, and cost. Nothing is wasted, though the tag lines are boilerplate rather than prose that earns emphasis.

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 required inputs plus cost are stated. However, for a 15-parameter chart computation where school/house-system choices change results, the description leaves the agent to infer everything optional from a partially documented schema, making it adequate but not complete.

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 coverage is only 33%, so the description is expected to compensate, yet it merely restates the four required parameters that the schema already marks as required. The numerous optional parameters that materially affect output (houseSystem, zodiacType, ayanamsa, fields, precision) are given no explanation in the description, leaving the low-coverage gap unfilled.

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 the specific artifact (Dasamsa / D10 divisional chart) and glosses its astrological domain (career, profession, public reputation), which meaningfully distinguishes it from the crowded varga family (d9 marriage, d7 children, etc.). It is clear what the tool produces, but it never explicitly contrasts itself with those sibling varga endpoints, so it stops short of a 5.

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 parenthetical domain hint implies when an agent would reach for D10 (career questions), but there is no explicit when-to-use/when-not-to-use statement and no named alternative among the ~20 sibling varga tools. Usage is inferable rather than stated.

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