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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered structurally. The description adds a genuinely useful behavioral fact, the 10-credit Tier 1 cost, but says nothing about output size, content depth, or what 'deep' means relative to other sign tools.

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?

Extremely short, which is good, but the leading poetic line carries no functional information and the only useful content is the Group/Cost tag block. Front-loading favors atmosphere over the detail an agent needs.

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 and full parameter coverage mean return-value detail is not required, but a paid content tool should still explain what depth of Cancer material it produces and how it differs from siblings. That framing is absent, leaving the agent to guess from the tool name alone.

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%, and both parameters (fields, precision) are compact-mode controls fully documented in the schema. The description contributes nothing about them, so the baseline 3 applies.

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 never states an action verb or what the tool returns; it is a poetic restatement of Cancer's traits ('Protective nurture, tidal memory. Ruler Moon. I FEEL.'). The bracketed '[Group: Zodiac Signs (Per-Sign Deep)]' tag is the only element that hints at the resource class, so an agent can infer the shape of the output but the tool's actual function is left implicit.

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?

No guidance on when to call this versus the eleven sibling per-sign tools or versus broader chart tools such as astroway_western_chart. The only actionable context is the cost line, which tells price but not usage conditions.

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