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

With annotations present, the description adds useful context beyond structured fields: the real-time streaming group and the 10-credit cost. However, it does not explain operational behavior such as whether the stream is a persistent connection, how data is consumed, or what authentication or rate limits apply. No annotation contradiction exists.

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 extremely concise and front-loads the core output before appending group and cost metadata. Every element earns its place, though '8-phase' is slightly cryptic without the lunar context from the title. It avoids waste and is easy to scan.

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 need not be explained; annotations and 100% schema coverage handle safety and parameters. The description still leaves the usage decision underspecified relative to the many sibling stream tools. It is adequate but not fully complete for an agent selecting among alternatives.

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%, so both optional parameters (fields and precision) are already fully documented in the input schema. The description contributes no additional parameter meaning, which is appropriate for the baseline score when the schema does the heavy lifting.

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 states the specific output: current lunar phase expressed as an 8-phase value plus a countdown to the next major phase. This makes the resource and scope clear, though it lacks an explicit verb like 'streams' or 'retrieves'. It is distinguishable from sibling stream tools by its lunar-phase 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?

No when-to-use guidance is provided. The group tag '[Group: Real-time Streaming]' implies a context, but it does not tell the agent when to choose this tool over alternatives such as astroway_stream_void_of_course or astroway_stream_ingress. There are no exclusions or alternative-routing instructions.

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