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

With no annotations, the description carries the full burden, and it does add real context: the default-to-now behavior and the '5 free trial calls per signed wallet' metering/auth signal. However it says nothing about error behavior for malformed dates, timezone handling, or precision of the returned fraction.

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?

One front-loaded sentence with no wasted phrasing; the returned fields appear before the pricing note. The emoji pricing tag is slightly off-topic for a capability description but costs little space.

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 trivial one-optional-parameter tool with no output schema, listing the three returned fields plus the default behavior is nearly sufficient. The only real gap is date input format, which the schema also omits.

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 coverage is 0% for the single date parameter, so the description must compensate. It does clarify that the parameter is optional and defaults to now, but gives no format guidance (ISO 8601, epoch, RFC 3339?), which is the most likely cause of a failed call.

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 gives a specific verb and a fully enumerated resource: it returns lunar phase fraction, phase name, and illumination for a date. An agent knows exactly what comes back. There is no close moon-related sibling to differentiate against, so it loses only the explicit-contrast credit.

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?

It states the date defaults to now, which implies the common call pattern, but offers no when-to-use vs when-not guidance and never references adjacent tools (e.g. x402-zodiac-sign, x402-easter-date, x402-julian-day). The agent must infer the usage context entirely.

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