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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a pure computation with defined outputs and reveals downstream sequencing, which is useful. However, it says nothing about permission/auth needs, determinism versus ephemeris recalculation, or how missing/partial inputs behave across the 9 parameters.

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?

Labeled WHEN TO USE / WHAT IT DOES / RETURNS / NEXT blocks make it front-loaded and scannable, and each section carries information. The RETURNS section partially duplicates the existing output schema, which is the one mildly wasteful element.

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 not explaining return values in depth is acceptable, and the when/next guidance is complete. But for a 9-parameter tool with 0% schema description coverage, the complete absence of parameter guidance is a real gap an agent cannot fill from structured data.

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 0% across 9 parameters, so the description must compensate and largely does not. It only incidentally implies target_year ("for the target year") and never explains units or formats for hour, minute, latitude, longitude, or timezone_offset, nor that lat/long have defaults.

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?

Uses a specific verb and resource ("Calculate the annual Tajaka solar return chart and aspects") and immediately disambiguates the sub-domain: Varshaphala chart, Muntha, and Tajaka aspects. This is distinguishable from Vedic siblings like calculate_birth_chart or calculate_varga_charts without opening schemas.

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?

Has an explicit WHEN TO USE clause plus a NEXT clause that routes to calculate_varshaphala for the full report and ask_cosmic_advisor for interpretation. The condition selecting each alternative is stated, not left to inference.

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