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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description usefully adds the cost (100 credits, Tier 4), which matters for budget-aware agents, but says nothing about latency, whether the interpretation is cached, or the consequences of the non-idempotent hint.

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 naming the resource and its output facets, plus two bracketed metadata lines for group and cost. Nothing is wasted, though the facet list is slightly padded and no sentence is spent on usage or behavior.

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 exists, so return values need not be explained, and the input schema is exhaustively documented. However, for a paid (100-credit) non-idempotent AI call, the description omits any note on when to prefer it over the other interpretation tools, leaving a gap in routing guidance.

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 chart objects are richly documented (timezone handling, ayanamsa, houseSystem letters, rejected short forms), so the schema does the heavy lifting. The description adds only 'between two charts', which loosely maps to chart1/chart2 but contributes no new parameter meaning.

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 (synastry between two charts), and enumerates what the output covers: relationship dynamics, attractions, friction points, long-term outlook. The phrase 'between two charts' implicitly separates it from single-chart siblings like astroway_ai_interpret_natal, though no sibling is named.

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 or when-not guidance, no prerequisites, and no named alternative among the many interpret_* siblings. The '[Group: AI Interpretations]' tag gives taxonomy context but not selection criteria; an agent must infer usage entirely from the tool name.

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