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 adds genuinely useful non-schema context: the cost (100 credits, Tier 4) and the AI-interpretation group, but says nothing about rate limits, determinism of the generated text, or latency.

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?

Front-loaded with the core purpose in the first clause, followed by a short use-case note and two compact metadata tags. No wasted prose, though the group/cost tags are structured metadata rather than prose value.

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 no explanation, and cost/group are disclosed. But the description claims the tool interprets 'a single chart element (planet/house/aspect)' while the schema exposes no field for selecting which element — the description leaves that mechanism unexplained.

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 body/fields/precision parameters are thoroughly documented in the schema itself, so the description carries no additional parameter burden. Baseline 3 is appropriate; the description adds nothing about how the target element is identified.

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 and resource ('AI interpretation of a single chart element (planet/house/aspect) in context'), and the 'single element' scope implicitly separates it from whole-chart siblings like ai_interpret_natal and synastry. However, it never names those siblings, so an agent must infer the boundary itself.

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 only usage cue is 'Useful for chart-detail pages,' which is a context hint rather than routing guidance. With four near-identical AI-interpretation siblings (natal, placement, synastry, transits), the description gives no explicit when-to-use/when-not or alternative selection rule.

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