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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it computes the chart, builds a prompt, and produces a 3-4 paragraph AI-generated message, plus the JSON return shape. It does not mention generation latency, cost, or any auth/rate-limit considerations for an AI-backed tool, leaving a modest gap.

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?

Front-loaded headers (WHEN TO USE / WHAT IT DOES / RETURNS / NEXT) make it scannable and each section adds distinct value. It is slightly verbose in prose but no sentence is redundant, so it stays close to an ideal structure.

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 the RETURNS line is a bonus rather than a necessity. Usage, purpose, and behavior are well covered for an AI-backed generation tool, but the total absence of parameter guidance against 9 undocumented inputs is the one real completeness gap.

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 but says nothing about any input. It never explains the birth date/time fields, the timezone_offset default of 5.5, or the latitude/longitude defaults, leaving the agent to infer everything from parameter names alone.

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+resource (generate a personalized daily horoscope from a birth chart) and explicitly differentiates itself from sibling get_daily_rashifal by contrasting chart-aware generation against the generic-paragraph service. An agent can distinguish it from calculate_birth_chart and get_weekly_horoscope without opening any schema.

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?

Provides an explicit WHEN TO USE clause naming the exact trigger (chart-aware daily prediction using birth chart, transits, dasha) and the anti-pattern it avoids (basic rashifal). The NEXT line routes the agent to calculate_birth_chart when only raw chart data is needed, giving a clear alternative.

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