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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context not in the schema: the cost (100 credits, Tier 4), the endpoint, and the group. It says nothing about latency, output format, or why idempotentHint is false, but the cost disclosure is meaningful added value.

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?

A single front-loaded sentence followed by compact bracketed metadata — nothing wasteful. The bracketed group/endpoint/cost lines are boilerplate but dense and useful rather than filler.

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-value explanation is not required, and the parameters are fully documented in the schema. However, with seven near-identical AI-interpretation siblings, the description omits the one thing most needed: which interpretation tool to pick. Adequate but with a clear routing gap.

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%, so the schema already documents body, fields, precision, and the planet/language parameters. The description adds no parameter semantics beyond what the schema provides, which is the correct baseline of 3 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+resource: 'AI interpretation of a specific planet+sign+house combination,' and the qualifier 'concise, focused on the placement only' signals scope. It somewhat differentiates from the natal/element/synastry siblings by narrowing to a single placement, but never names them.

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 among the six other astroway_ai_interpret_* siblings. The agent must infer that 'placement only' contrasts with natal/element interpretations without any explicit instruction.

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