Stream Positions

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

Description says 'snapshot' which implies read-only access, but annotations set readOnlyHint=false, creating a contradiction. No explanation of behavioral traits such as whether it establishes a persistent stream or returns a one-time result.

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 with two lines, no wasted text, and front-loads the key purpose: 'Current planetary positions snapshot, tickSeconds=30.'

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?

Despite minimal parameters and a contradictory annotation, the description lacks essential context such as output format, whether it starts a stream or returns a single snapshot, and how to interact with it. More detail is needed for a real-time tool.

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?

There are zero parameters, so the description does not need to add any. Schema coverage is 100%, and the description correctly provides an example request body {}.

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 it provides a 'Current planetary positions snapshot' with a tick interval of 30 seconds, which is specific and actionable. However, it does not differentiate from sibling streaming tools like stream_eclipse_incoming or stream_ingress, but the purpose is still clear.

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 guidance on when to use this tool versus other streaming tools. The grouping '[Group: Real-time Streaming]' implies real-time use, but no explicit alternatives or conditions are provided.

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