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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety semantics are covered by structured data. The description adds genuinely useful non-annotation context: the POST endpoint and the 20-credit Tier 2 cost, which an agent needs for budget planning. It says nothing about rate limits, latency, or what the response contains beyond the existence of an output schema.

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 purpose is front-loaded in a single clause, followed by bracketed metadata that is dense and skimmable. The 'Required' line duplicates the schema's required array and is the one element that does not earn its place; everything else (group, endpoint, cost tier) is actionable.

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 chart computation with an output schema, the description covers identity, endpoint, and cost but omits any interpretive framing or parameter guidance beyond the required list. An agent can call it correctly but has no help choosing ayanamsa, house system, or zodiac type, which materially affect a varga chart.

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%, so the description is expected to compensate but does not: it merely restates the four required parameters, which the schema's required array already declares, earning no credit. The many optional parameters (ayanamsa, houseSystem, zodiacType, fields, precision, cosmogram) are neither explained nor linked to the chart's interpretation choices.

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 a specific chart type (Chaturthamsa / D4) and maps it to domains (fortune, fixed assets, real estate), which is the standard signification set for the fourth divisional chart. Combined with the D4 label and endpoint, an agent can distinguish it from the D1/D9/D10 varga siblings. It stops short of explicitly contrasting itself with those siblings, so it falls just under 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?

There is no when-to-use or when-not-to-use guidance, and no mention of the alternative varga tools. The only routing aid is the domain gloss (real estate, assets), which an agent must interpret on its own. A brief 'use for property/asset analysis instead of D1' line would have closed this gap.

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