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

Annotations already declare readOnly=true, destructive=false, and importantly idempotent=false. The description adds genuinely useful behavioral context via the cost line ('100 credits (Tier 4)'), which annotations do not convey. It stops short of noting that output is LLM-generated and non-deterministic (consistent with idempotentHint=false) or any latency/rate-limit expectation.

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?

A single front-loaded sentence states the purpose, followed by compact metadata tags. Nothing is redundant or padded, though the group/cost tags are more structured metadata than prose.

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?

The tool takes a two-part input (natal birth data plus a required transitDate/time), and the description never surfaces that both halves are needed or that the transit date drives the interpretation window. An output schema exists so return values need not be explained, but for a Tier-4 credit-consuming interpretation tool the description would benefit from a note on the required transit date and non-determinism.

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 nested birth-data object, fields, and precision parameters are already fully documented in the schema, including the rejected short-form names and the timezone/timezoneOffset rules. The description adds no parameter-level information, so the baseline of 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?

States a specific verb ('AI interpretation') and resource ('current/upcoming transits to a natal chart') plus the scope of output ('what each major transit means in life context'). It is clear on its own, but it does not differentiate itself from close siblings such as astroway_ai_interpret_natal or astroway_mcp_ai_explain_transit, leaving the agent to infer the boundary.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named. The '[Group: AI Interpretations]' tag offers weak categorization but no condition that tells an agent when to pick this over the natal, placement, or synastry interpreters. The cost tier is stated but is not usage guidance.

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