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

No annotations are present, so the description carries the full behavioral burden. It does disclose the computed outputs and return shape, which is useful, but it never states that this is a read-only, side-effect-free calculation, nor does it address the India-centric defaults (lat 20.59, lon 78.96, tz 5.5) or ayanamsa sensitivity that materially affect results.

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 with the one-line purpose, then cleanly partitioned into WHEN TO USE / WHAT IT DOES / RETURNS. Labels are efficient, though the RETURNS block partially duplicates the existing output schema, which adds some redundancy.

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?

Because an output schema exists, the return enumeration is not strictly needed, and the main gap is the undocumented parameter set at 0% coverage for a complex 8-parameter astronomical calculation. The description is serviceable for invocation but incomplete on the inputs an agent must reason about.

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 coverage is 0% across 8 parameters, so the description must compensate. It conveys date and location inputs generally ('at the given date and location') but says nothing about hour, timezone_offset, or ayanamsa_mode, which are all result-affecting. Five of eight parameters remain semantically undocumented.

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 and resource ('Calculate current planetary transit positions for a date') and defines what is computed (sidereal longitudes, nakshatras, signs, houses, retrograde status). It gives strong domain framing (gochara, mundane astrology) but does not explicitly distinguish itself from siblings like get_weekly_transit_events, so it stops short of 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?

The 'WHEN TO USE' line gives clear triggering context ('where planets are right now or on a specific date for transit analysis'). However, it names no alternatives or exclusions, leaving the agent to infer when this beats get_weekly_transit_events or find_auspicious_times.

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