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. The description adds genuinely useful context beyond them: the output includes illumination metrics alongside the SVG, and the call costs 10 credits (Tier 1). It does not, however, mention the format/theme/size switch behavior that matters for a render tool.

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 front-loaded sentences covering what is rendered and what is returned, followed by terse metadata tags. Nothing is padded or repetitive, though the metadata lines contribute no semantic guidance.

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?

Search is not needed: the description is complete for its scope. An output schema exists, so return values need not be detailed, and the description still notes SVG plus illumination metrics. The only true gap is sibling disambiguation, which is minor given the distinct 'render' namespace.

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%, including rich prose on timezone, coordinates, house system and the css theme, so the schema carries the parameter burden. The description only echoes 'at the given moment', adding nothing about date/time, precision, or fields beyond what the schema documents. Baseline 3 applies.

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 (Render) and resource (the moon disk with its illuminated fraction) scoped to a moment in time. This is clear enough to distinguish it from most render siblings, but it never addresses the obvious near-neighbor astroway_calendar_moon_phase, which also deals with moon 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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as astroway_calendar_moon_phase for raw phase data versus this tool for a visual disk. The only usage-adjacent signal is the bracketed cost and group tag.

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