Daily Horoscope

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description adds the genuinely useful behavioral fact that plain-style text is generated once in English then translated, and that output is model-written. It does not mention the 50-credit cost, which is a material trait for a metered tool.

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?

Purpose is front-loaded and the parameter sentence earns its place. The long enumeration of returned keys (sections, transits, aspects, events, energy, lucky, compatibleSigns) largely duplicates the existing output schema and inflates the definition.

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?

Given seven parameters, rich annotations and an output schema that covers return values, the description supplies enough to call the tool correctly for the main options (style/length/topics/language). Remaining gaps — what `date` does when omitted and what `disclaimer_inline` toggles — are minor but real.

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 description meaningfully explains `style`, `length` and `topics` — including the non-obvious point that `plain` is written once in English and translated so all languages agree — and confirms the 21-language scope for `language`. It says nothing about `date` (format, whether it defaults to today) or `disclaimer_inline`, which are undocumented in the schema too, so the 43% coverage gap is only partly closed.

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 gives a specific verb and resource ('Daily horoscope for a zodiac sign') plus the generation basis (solar houses and the day's transits), so an agent knows exactly what this produces. Differentiation from the weekly/monthly/yearly siblings is implied only by the word 'daily' and 'the day's transits', not stated explicitly.

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 explicit when-to-use statement, no exclusion, and no named alternative among astroway_horoscope_weekly, _monthly, _yearly or astroway_horoscope_compatibility. Usage is only implied by the name and the 'the day's transits' framing.

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