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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: it discloses a 2-credit cost, notes that some fields require paid tiers, and lists extra outputs such as mood, lucky numbers, sign compatibility, and sign facts. It still lacks auth or rate-limit details, but for a read-only lookup this is solid transparency.

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 purpose and cost are front-loaded, and the description is compact while listing relevant feature details. It wastes some space repeating 'Horoscope: Horoscope' and could separate paid-tier details more cleanly from basic usage, but it remains readable and efficient.

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 five optional parameters, 100% schema coverage, an output schema, and annotations covering safety, the description supplies the essential context: what is fetched, how to trigger it, cost, and paid-tier additions. It is slightly incomplete because it frames the tool as 'daily' even though the schema supports weekly/monthly and tomorrow/yesterday, though the schema itself documents those options.

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 100%, so the input schema already documents all five parameters. The description adds some context by identifying sign name as the basic input and birthdate as a paid-tier lookup, but it does not explain period, tomorrow, or yesterday or add format details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

It states a specific verb ('fetches') and resource ('daily horoscope readings and sign details') and scopes the tool to 'any of the twelve zodiac signs,' so an agent can identify the core purpose. It does not explicitly name or differentiate from siblings such as ChineseZodiac or BirthChart, so it falls 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?

It tells the caller to 'Pass a sign name to receive today's forecast text' and notes paid-tier features, which gives clear implied usage for horoscope retrieval. However, it provides no explicit when-to-use-vs-alternatives guidance, no exclusions, and no prose guidance on choosing among period, tomorrow, or yesterday beyond what the schema states.

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