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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful output-side context — the report spans Vargas, Yogas, current Dasha and upcoming Antardashas, and interpretations are 'qualified and evidence-linked' — but says nothing about generation cost, latency, or how the current-timing section depends on asOfDate/horizonYears.

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 verb and purpose are front-loaded, but the 18-item topic run-on bloats a single sentence and largely restates what the report covers rather than adding selection guidance. It is dense without being well-structured for an agent choosing between tools.

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 the annotations cover safety. However, for a 13-parameter tool with 7 required birth-data fields and near-zero schema descriptions, the definition leaves the agent without input guidance and without routing advice against the large sibling set.

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 13 parameters and only 8% schema description coverage, the description carries the burden of explaining inputs, yet it names none of them. The enumerated life areas loosely correspond to some focus enum values (career, marriage, education, property, health, spirituality), but nothing explains focus, language, horizonYears, asOfDate, or birthTimeAccuracyMinutes.

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 verb ('Builds') and a well-defined resource ('normal-person South Indian astrology report'), then enumerates the coverage so an agent can see it is broader than the narrow analyze_* siblings. It never names an alternative such as get_full_life_report_section or generate_report_pdf, so sibling differentiation is implied by breadth rather than stated.

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 exhaustive topic list implies this is the comprehensive, one-shot report generator rather than a per-topic analyze_* call, but there is no explicit when-to-use / when-not-to-use statement and no comparison with get_full_life_report_section or generate_report_pdf. Usage must be inferred from the sibling names.

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