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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds one piece of real operational context beyond the annotations: the 10-credit Tier 1 cost, which affects an agent's decision to call it. It says nothing about the computation basis, required auth, or what a lunation phase result contains.

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?

The text is short, front-loaded, and free of filler, which is good, but it is under-specified rather than concise in the productive sense. The bracketed tags consume the entire body and deliver only taxonomy and pricing, leaving no room for scope or constraints.

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?

For a tool with 15 parameters, 4 required, and only 33% schema coverage, the description is far too thin; the one mitigating factor is that an output schema exists, so return values need not be explained. It is still missing the input premise (that a date/time/location is needed), any exclusion guidance, and any note on how the 8-phase result is produced.

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 only 33%, so the description bears responsibility for clarifying the remaining parameters, and it contributes nothing about any of the 15. The four required parameters (date, time, latitude, longitude) have no schema descriptions at all, and the description does not indicate that they must describe the birth/lunation moment. No syntax, units, or defaults are explained.

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?

The description is essentially the title restated with a qualifier: "8-phase lunation classification" against the name/title "Lunation Phase." It never states what the classification is computed from (a natal chart? a birth moment? transits?) even though the required parameters (date, time, latitude, longitude) imply chart calculation. It also gives no differentiation from the near-identical sibling astroway_psyr_lunation_phase.

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 guidance, no prerequisites, and no mention of alternatives among the many lunation/cycle siblings (rudhyar_cycles_of_becoming, psyr_lunation_phase, etc.). The [Group] and [Cost] tags are taxonomy and billing metadata, not usage guidance. An agent has nothing to route on other than the name.

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