Stream Void-of-Course

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description's main added value is the cost of 10 credits (Tier 1) and the POST endpoint, both absent from annotations. However, it never clarifies what 'stream' means here — whether the call returns a single snapshot or opens a live subscription — which is exactly the behavioral detail an agent needs. No contradiction with annotations, since a POST-compute call is consistent with readOnlyHint=false.

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 substantive sentence is front-loaded and waste-free, and the bracketed metadata lines are scannable rather than prose clutter. It is arguably too short for the payload's nuance, but nothing is padded.

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-value documentation is not required, and a no-param tool needs no input guidance. The remaining gap is conceptual: the 'stream' framing and POST endpoint leave ambiguous whether the caller gets one VOC snapshot or a continuous feed, which matters for how an agent would invoke and consume it.

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?

With zero input parameters there is nothing for the description to disambiguate, so the baseline of 4 applies. The description adds no misleading parameter hints, though it also doesn't state that the call requires no arguments.

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 exact payload: current Moon void-of-course status plus the next ingress. That is a specific resource with a clear scope, and the 'Real-time Streaming' group label situates it among the stream siblings. It stops short of naming how it differs from the very similar astroway_calendar_moon_voc or astroway_horary_moon_voc siblings, so an agent must infer the distinction.

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?

There is no explicit when-to-use statement and no named alternative. The 'Real-time Streaming' group tag implies a now-focused use case, but nothing tells the agent when to pick this over calendar_moon_voc or horary_moon_voc, nor any precondition for calling it.

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