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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that results are derived from Shadbala strength, which is useful interpretive context. It says nothing about determinism of the returned values, response shape, or the impact of an approximate birth time (the schema hints 12:00 fallback but the description does not warn about degraded accuracy).

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 front-loaded sentence that enumerates the outputs without preamble or filler. The list is somewhat dense but every item corresponds to an actual returned value, so nothing is wasted.

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?

With no output schema, the description must convey what comes back, and it does: day, colour, number, metal, direction, and a per-weekday lucky/neutral/challenging breakdown. Required birth inputs are fully documented in the schema. The remaining gap is the absence of any note about accuracy when birth time is approximate.

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 100% with 7 parameters, each documented in the schema (date/time formats, lat/long ranges, timezone default, optional name/place). The description adds no parameter-level meaning beyond that. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 the concrete artifacts returned (lucky day, colour, number, metal, direction) and the derivation method (strongest planet via Shadbala), plus the weekday lucky/neutral/challenging classification. That is specific enough to distinguish it from generic report tools. It stops short of explicitly contrasting itself with close siblings such as planet_strength or numerology.

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?

There is no statement of when to call this tool, what prerequisites exist (e.g. that a full birth chart must be computable from date/time/place), or how it differs from planet_strength, kundali_strength or numerology. The agent must infer usage entirely from the output list.

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