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 the credit cost (10 credits, Tier 1) and group membership, which is useful behavioral context, but it does not describe output content or any other operational traits.

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 short and the tag structure is efficient, but the opening sentence is poetic rather than front-loaded with purpose. For tool selection, the first line does not earn its place as functional information.

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 per-sign deep-dive tool with an output schema and safety annotations, the description fails to state what the tool returns or how it differs from other per-sign deep tools. The name and title give some context, but the description itself is too incomplete for an agent to confidently select it.

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%, so both parameters (fields and precision) are fully documented in the schema. The description adds no parameter meaning. Baseline 3 applies 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?

The description consists of astrological keywords for Leo ('Radiant generosity, theatrical authority. Ruler Sun. I WILL.') rather than a functional statement of what the tool does. It never says it returns a deep interpretation of the Leo zodiac sign, leaving only the title and group tag to infer purpose.

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 guidance on when to use this tool versus the many sibling per-sign deep tools (e.g., aquarius, aries) or other zodiac tools. The description provides only a cost tag, not usage context or alternatives.

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