pause_level_sequence_runtime

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

Beyond the annotations, it discloses that pausing preserves the current position, that the player is bound to the PIE/game world lifetime, and exactly what the call returns. It does not explain permission/auth requirements, but the lifecycle and state-preservation context is substantive. Note the mild tension with destructiveHint=true, since pausing at the current position is a state-preserving operation; the description does not contradict the annotation so much as leave the destructive signal unexplained.

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?

Front-loaded with the action and target, and the trailing lifecycle caveat is useful. Slight waste: the final 'Returns: {...}' block restates the return fields already listed in the preceding sentence, so the same information is delivered twice.

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?

For a one-parameter runtime mutation with no output schema, the description supplies the return shape, the state semantics, the world-lifetime constraint, and the follow-up read tool. The only remaining gap is that the destructiveHint annotation is not reconciled with the evidently reversible pause behavior.

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% and the single player_key parameter is already documented there as coming from play_level_sequence_runtime. The description repeats that provenance but adds no new syntax, format, or validity nuance, so the baseline 3 applies.

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?

States a specific verb (pauses) plus the exact resource (the runtime ULevelSequencePlayer identified by player_key) and pins the key's origin to play_level_sequence_runtime. An agent can separate this from play_level_sequence_runtime, stop_level_sequence_runtime, pause_timeline and get_level_sequence_status_runtime without opening any schema.

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?

Routes the agent to the read-side alternative explicitly ('read it later with get_level_sequence_status_runtime') and gives the lifecycle boundary ('stop resolving once it ends') that tells when the tool is applicable. There is no explicit when-not-to-use clause, so it falls just short of a 5.

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