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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and non-openWorld, so the safety profile is covered. The description usefully adds the cost dimension ('10 credits (Tier 1)'), which is genuine behavioral context an agent needs for budgeting, but it says nothing about what content is returned or any rate/auth considerations.

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?

It is short and free of padding, but it front-loads thematic flavor text rather than function, and the only operationally useful elements (group, cost) are tucked into trailing brackets. Brevity is good; information ordering serves the agent poorly.

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 an output schema and full parameter coverage, return format and argument details are legitimately omitted. However, for a content-retrieval tool the description never says what the tool actually delivers or how it differs from its eleven siblings, leaving the core selection question unanswered.

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% with only two optional parameters (fields, precision), both fully documented in the schema itself. The description adds no parameter-level information, so the baseline 3 applies — the schema carries the semantics entirely.

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's main sentence ('Pioneering will, raw initiation. Ruler Mars. I AM signature.') describes the astrological character of Aries rather than what the tool does or returns. It never states a verb+resource such as 'returns deep per-sign content for Aries.' Only the name, title, and bracketed group label identify the function, making this close to a thematic restatement rather than a purpose statement.

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 and no routing to alternatives. The '[Group: Zodiac Signs (Per-Sign Deep)]' tag situates it in a family but does not explain when an agent should pick this over the other eleven sign tools or the general western chart tools. Nothing states what input, if any, this content tool expects or when it is appropriate to spend the 10 credits.

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