Stream Planetary Hour Changes

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

Annotations include readOnlyHint=false, but streaming is inherently read-only, creating a contradiction. The description adds no behavioral context beyond the group label (e.g., connection management, rate limits, or that this is an SSE stream).

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?

Very short and front-loaded: the core purpose is in the first sentence. The group label and example are useful but not redundant. Could be slightly more efficient, but overall appropriate length.

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?

No output schema exists, so the description should indicate the stream's data format (e.g., timestamps, planetary hour identifiers). It only mentions 'planetary hour + next 24' without return structure. The streaming nature (SSE?) is implied but not specified. Incomplete for a 3-parameter tool with no output schema.

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 0%, so the description should explain parameters. The example shows values but does not clarify that latitude/longitude specify the location or that timezoneOffset adjusts time. The schema already provides basic types, but the description adds little meaning.

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 'Current planetary hour + next 24' clearly specifies the resource (planetary hour changes) and time scope (current and next 24 hours), distinguishing it from non-streaming siblings like 'planetary_hours'.

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 explicit guidance on when to use this tool vs alternatives. The group label 'Real-time Streaming' implies use for live updates, but the description does not directly contrast with sibling 'planetary_hours' or state exclusions.

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