watch_game_state

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

No annotations provided, so the description carries the behavioral burden. It discloses push-on-change semantics (event-driven, not polled) which is a meaningful behavioral trait beyond the empty schema, and names a stop mechanism. Does not disclose notification payload format or delivery guarantees.

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?

Three short sentences, front-loaded with the action, then the mechanism, then the teardown. No filler.

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?

Covers the what, the when-alternative, and the teardown for a zero-param subscription tool. No output schema, but the push-notification payload shape is not described; minor gap since notification content (position, health, animation state) is at least hinted.

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?

Zero parameters, so baseline is 4. Description correctly implies no parameters are needed to start the subscription.

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?

Names the specific action (subscribe to real-time game state updates) and the resource (game state). Distinguishes from the polling alternative get_objects and pairs with the sibling unwatch_game_state.

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?

Explicitly frames when to use: instead of repeatedly calling get_objects. Also states how to stop by tying to unwatch_game_state. No explicit when-not-to-use, but the alternative is named clearly.

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