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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds genuinely useful operational context: token caching for repeated calls, multi-language output, the POST endpoint, and the 100-credit Tier 4 cost. It does not state what the AI output format is, but the output schema exists.

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?

One front-loaded sentence captures the purpose and output content, followed by short metadata lines for language, caching, group, endpoint, and cost. Efficient, though the bracket-tag lines are somewhat boilerplate rather than description 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?

With a full output schema, return values need not be explained, and the cost/endpoint/caching details round out what an agent needs. The one real gap is sibling disambiguation among the interpret_* family, which the description never addresses.

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 body object documents birth-data fields, timezone rules, and house-system letters in detail. The description adds nothing about body, fields, or precision, so the baseline 3 applies 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?

States a specific verb (Generate AI interpretation) and resource (natal chart), and enumerates the output content (personality traits, life themes, strongest archetypes). It does not explicitly differentiate itself from the many sibling interpret_* tools (element, placement, synastry, transits), leaving the agent to infer 'natal' means the whole birth chart.

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 guidance, no exclusions, and no routing to alternatives such as astroway_ai_interpret_transits or astroway_ai_interpret_synastry. The only contextual cue is the [Group: AI Interpretations] tag, which 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.