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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description does add genuinely useful non-annotation context, the credit cost (10 credits, Tier 1) and the endpoint/group, but says nothing about response shape, whether results vary with the sidereal options, or any auth/billing prerequisites.

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?

The definition is a single front-loaded purpose line followed by compact bracketed metadata, with no filler sentences. It is efficiently structured, though the metadata tags substitute for substance rather than complement it.

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?

For a 15-parameter chart-driven tool, the description leaves most parameter semantics and any derivation logic (how the sign is computed) unexplained. Output schema and annotations carry part of the burden, but the definition is not complete enough for an agent to call this confidently without inspecting the full schema.

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 only 33% across 15 parameters. The description's '[Required: date, time, latitude, longitude]' merely duplicates the schema's required array, and it says nothing about the many computation-affecting parameters (ayanamsa, zodiacType, houseSystem, fields, precision). It therefore adds essentially no semantic value beyond the structured fields.

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 outputs (yoga focus, asanas, pranayama) and scopes them to a sign, which distinguishes it from the other wellness siblings (diet, exercise, crystals, sleep). However, it never says how the sign is derived from the date/time/latitude/longitude inputs, so the 'sign-specific' premise is left vague for an agent that must decide whether this tool fits a user's request.

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 only guidance is a '[Required: ...]' tag listing inputs, which is not the same as when-to-use/when-not-to-use or naming an alternative. There is no indication of what kind of user request should route here versus astroway_wellness_exercise or astroway_wellness_medical_astrology.

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