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

With no annotations, the description carries the full behavioral burden; it implies a read-only snapshot by describing returned data but never states so outright. It omits ephemeris source, computation latency, and whether results are live or cached. For a zero-parameter read tool the risk is low, so the gap is moderate rather than severe.

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?

A single dense sentence that front-loads the two zodiac systems and then enumerates the bodies and the retrograde flag. No filler, no repetition of the title.

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?

There is no output schema, so the description must convey return values – and it does, specifying signs, degrees, both zodiac conventions, and retrograde flags. What remains unstated is the response shape (per-planet objects vs. a list) and any handling of unavailable bodies, which is a minor gap for a simple snapshot tool.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object and the description correctly implies no inputs are required.

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 contents: current signs and degrees for the Sun, Moon and planets in both tropical and sidereal Lahiri zodiacs, with retrograde flags. The word 'current' implicitly separates it from a birth-chart tool, but it does not explicitly contrast itself with siblings like get_sign_ingresses or get_retrograde_periods.

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?

Usage is only implied by 'Current' – an agent can infer this is a now-snapshot rather than a historical range or a natal calculation. There is no explicit statement of when to pick this over get_retrograde_periods or get_sign_ingresses, and no prerequisites are mentioned.

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