Set Playdate Simulator pause state

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

Annotations already cover key behavioral traits: readOnlyHint=false indicates mutation, idempotentHint=true indicates repeated calls are safe, and destructiveHint=false indicates no destruction. The description adds the context that it targets the running game, but does not describe error cases or output behavior; the existing output schema and annotations carry much of that burden.

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 a single short sentence, 'Pause or resume the running game,' that immediately conveys the action and target with no wasted words. It is appropriately sized for a simple state-setting tool.

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 two-parameter tool with full schema coverage, clear annotations, and an output schema present, this description is sufficient. The schema explains pid and paused semantics, and the annotations cover idempotency and safety, so nothing critical is missing.

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%, so the schema already documents pid and paused thoroughly, including that paused is 'True to pause; false to resume.' The description adds no additional parameter meaning, so the baseline of 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?

The description uses a clear verb and object: 'Pause or resume the running game.' It accurately identifies the operation and is distinguishable from siblings like playdate_run and playdate_set_button, though it does not explicitly contrast itself with them.

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?

Usage is implied by the phrase 'the running game,' suggesting the tool is appropriate when a game is already active and needs pausing or resuming. However, there is no explicit guidance about alternatives or when not to use this tool.

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