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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description genuinely adds cost metadata not present in structured fields ('10 credits (Tier 1)') plus the group membership, but says nothing about what the payload contains or how large it is.

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 text is brief and not padded, and the group/cost tags are efficiently placed. However, the leading sentences are poetic branding rather than front-loaded functional information, so the space is spent on material that does not help tool selection.

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?

An output schema exists, so return values need not be described, and the tool requires no inputs. Still, for a paid content-retrieval tool the description never confirms it returns a textual/interpretive deep dive for Pisces, leaving an agent to rely entirely on the tool name.

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 the two optional parameters (fields, precision) are fully documented in the schema with examples. The description adds nothing beyond the schema, which is the expected baseline 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 is evocative flavor text ('Oceanic compassion, dissolving boundaries. Jupiter + Neptune. I BELIEVE.') that never states what the tool does or returns. The name, title and '[Group: Zodiac Signs (Per-Sign Deep)]' tag carry the entire functional load, so the description essentially restates the resource identity rather than clarifying 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 when-to-use guidance, no when-not-to-use, and no reference to the sibling sign tools (aries, taurus, etc.) despite there being eleven equivalents in the toolset. An agent must infer from the name alone that this returns Pisces-specific deep content and that the other signs have their own entries.

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