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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful operational context (cost of 100 credits, Tier 4, endpoint path), but says nothing about latency, auth, or what the AI interpretation actually consists of.

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?

Two short sentences, front-loaded with the purpose, followed by clearly delimited group/endpoint/cost metadata. Nothing is padded, though the one-line usage hint is thin relative to the space it occupies.

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 format need not be described, and cost/endpoint metadata is a nice addition. But for a tool whose whole premise is interpreting "a single chart element," the absence of any stated way to select that element (in description or schema) leaves a real completeness hole.

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 object is documented in exhaustive detail, so the baseline is 3. The description adds nothing beyond the schema, and notably neither the description nor the schema exposes any parameter identifying WHICH planet/house/aspect is being interpreted, which is a semantic gap an agent would want addressed.

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 clear verb+resource: AI interpretation of a single chart element (planet/house/aspect) with context. However it does not distinguish itself from the close sibling astroway_ai_interpret_placement, which appears to cover similar single-element territory, so an agent cannot confidently choose between them from the text 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?

"Useful for chart-detail pages" implies the intended context but gives no when-not guidance and never names an alternative among the many astroway_ai_interpret_* siblings. The usage signal is suggestive rather than directive.

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