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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds substantial context beyond that: it is Group Reports, costs 5,000 credits (Tier 7, ~50% of the free monthly budget), and requires user confirmation. Credit cost and budget impact are genuinely valuable and not derivable from annotations, though it doesn't clarify whether each invocation consumes credits again (non-idempotent).

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 content list is front-loaded and dense with concrete deliverables, followed by clearly tagged [Group] and [Cost] lines. Every element earns its place with no filler, though the trailing confirmation note is appended without much structural integration.

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-value details are rightly omitted, and the description adequately conveys what the generated report contains plus its credit cost. The main gap is that the 'PDF or HTML' output choice from the title is never explained or tied to a parameter, leaving the delivery format ambiguous.

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?

With 60% schema description coverage, the schema does most of the work, and the description adds only the Lahiri default (mapping to the ayanamsa parameter). It gives no guidance on fields, precision, language, or whitelabel behavior. This is the baseline 'schema carries it' case, with only marginal added value.

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 resource and its scope: 'Sidereal Vedic chart (Lahiri ayanamsa)' with Lagna, nakshatra/pada, planet positions, and a 9-period Vimshottari Mahadasha tree. This is far more specific than a tautology and implicitly distinguishes it from tropical/natal siblings by emphasizing 'Sidereal Vedic'. However, it never explicitly names the sibling it differs from (e.g. reports_natal), so an agent must infer the routing.

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 only routing guidance is the cost guardrail: 'Confirm with user before invoking' for a Tier 7 tool. That is useful but concerns approval, not selection. There is no statement of when to choose a Vedic Kundli over astroway_reports_natal, human_design, or the other report siblings, leaving usage to inference.

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