Moon-Phase Sleep Tips

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which convey safety. The description adds no behavioral context beyond stating the tool's purpose, such as authentication needs, rate limits, or error handling. No contradiction with annotations.

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 description is concise (one sentence plus group tag and example), with the core action front-loaded. Every element serves a purpose: clear purpose, grouping hint, and illustrative example. No superfluous content.

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 read-only tool with strong annotations, the description adequately covers the tool's purpose. It specifies input (date) and output (sleep recommendations per moon phase). No output schema exists, but the description implies natural language tips, which is sufficient for this context.

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 clear parameter descriptions. The description does not add meaning beyond the schema; the example shows typical usage but does not explain optional parameters (latitude, longitude, timezoneOffset) further. Baseline score of 3 is appropriate.

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 'Sleep recommendations per moon phase' uses a specific verb ('recommendations') and resource ('sleep per moon phase'), clearly distinguishing it from sibling wellness tools like wellness_diet or wellness_exercise. The title 'Moon-Phase Sleep Tips' reinforces the focus.

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?

The description hints at a complementary tool by stating 'Pair with /sun-times to find current phase', providing cross-reference but no explicit guidance on when to use this tool versus alternatives (e.g., other wellness tools). It does not exclude misuse or clarify context.

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