Get upcoming moon phases - Next new moon, full moon, quarters

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it returns dates and phase names for each lunar quarter and is scoped to upcoming weeks/months, but does not disclose details like timezone handling or boundary conditions. No contradiction.

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 sentences with no waste: the first front-loads the action and return value, the second gives concrete use cases. Nothing repeats the schema or annotations.

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 simple, parameter-optional query tool, the description combined with full schema coverage, annotations, and an output schema is sufficient to invoke correctly. The only gap is not explicitly routing the agent away from sibling moon-phase tools.

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%, with lang, count, compact, and startDate all documented with defaults, constraints, and examples. The description adds no parameter-specific semantics, so the 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 and resource: 'Get upcoming moon phase transitions' and names all four phases. 'Upcoming' and 'next weeks/months' clearly separate it from sibling tools like get_astrology_moon_phase_current and get_astrology_moon_phase_calendar_year_month.

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?

Provides clear context with use cases: 'Perfect for lunar event calendars, moon phase widgets, and astrology planning tools.' It does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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