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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the per-call cost (20 credits, Tier 2) and the endpoint, but says nothing about failure modes, rate limits, or what the computation produces.

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 bracketed metadata block is compact and front-loads the essential purpose before plumbing details. Every line carries information, though the '[Required]' line duplicates the schema's required array rather than earning its place.

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 sitting in a family of 16 near-identical varga tools, the description does little to orient the agent: no optional-parameter guidance despite 33% schema coverage and no differentiation from the sibling varga charts. The presence of an output schema excuses it from explaining return values, but the input-side and routing gaps remain.

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 33% across 15 parameters, and the description merely repeats the four required names (date, time, latitude, longitude) that the schema already marks required. Eleven optional parameters — including fields, precision, zodiacType, houseSystem, ayanamsaId — receive no guidance from the description to compensate for the coverage gap.

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 a specific resource (Saptamsa / D7 divisional chart) plus its astrological signification (children, progeny), which lets an agent tell it apart from the other varga siblings by domain. It stops short of explicitly contrasting itself with those siblings, but the verb+resource is unambiguous.

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 '(children, progeny)' implies the domain in which this chart is relevant, so usage is inferable. However, there is no explicit when-to-use, no condition selecting D7 over D1/D9 or the other 15 varga tools, and no stated prerequisites beyond the required parameter list.

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