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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld). The description goes beyond them by disclosing cost (100 credits, Tier 4) and result caching for repeated inputs — both materially affect whether an agent calls it, and repeated calls are hinted non-idempotent yet cached, which is worth knowing. It does not say anything about latency despite the AI-generation nature of the call.

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?

Very short and front-loaded: purpose first, then language support, caching, cost. The bracket tags ([Group], [Cost]) are functional but slightly metadata-ish rather than prose; still, nothing is wasted or buried.

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 present, the description needn't explain return values, and the input schema is fully documented. It covers what the interpretation contains, language options, caching and credit cost for a paid AI-generation endpoint. The remaining gap is the absence of any latency/streaming or failure-mode note for a long-running generative call.

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 the nested birth-data schema is exhaustively documented (field names, timezone rules, houseSystem letters, compact-mode fields/precision). The description adds nothing about parameters, which is acceptable given the schema carries the full burden — this lands on the baseline 3.

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+resource ('Generate AI interpretation of a natal chart') and enumerates the output content (personality traits, life themes, strongest archetypes). The natal-chart scope implicitly separates it from astroway_ai_interpret_synastry, _transits, _element and _placement, but those siblings are never named, so the agent must infer the division of labor from the tool name alone.

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?

The description never says when to choose this over astroway_ai_interpret_placement or astroway_ai_interpret_synastry, nor what prerequisites exist (a computed chart?). 'Multi-language' and 'token-cached for repeats' are properties, not usage conditions, so selection guidance is left entirely to inference.

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