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

No annotations are present, so the description carries the behavioral burden. It does add one useful trait ('offline'), suggesting no network dependency, but it does not disclose output details, timezone handling, or how 'current' is determined.

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 one short sentence and immediately front-loads the core purpose. The only minor redundancy is the 'Moon Phase:' prefix, which echoes the tool name.

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?

An output schema exists, so return values do not need explanation, but the undocumented `q` parameter and lack of usage context leave a meaningful gap. The description is too thin for an agent to confidently decide what to pass in.

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% and the description says nothing about the single `q` parameter. Since the schema provides no description either, an agent has no way to know what `q` means or how to populate it.

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 clearly states the resource ('moon phase') and the data returned ('current moon phase & illumination'). It does not use a verb, but the intent is unmistakable and it is not easily confused with any nearby sibling tool.

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 intended use is implied: when the user wants the current moon phase, use this tool. However, there is no explicit when-to-use guidance, exclusions, or comparison to alternatives, though no closely related sibling exists in the list.

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