Control non-interactive Playdate GIF recording

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

The description goes beyond annotations by disclosing that recording state is owned by the Simulator agent, not the MCP server, which is crucial behavioral context. It also clarifies that starting uses a new GIF path while stopping finalizes the active recording. Edge cases like repeated start calls or stopping with no active recording are not covered, but the annotations already signal mutation and non-idempotency.

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 two sentences with no filler. The first sentence states the core behavior, and the second adds essential state-ownership context, both earning their place.

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?

The description covers the two modes of operation and the key external-state caveat, while an output schema exists to document return values. It is sufficiently complete for an agent to select and invoke the tool correctly, though behavior during edge cases such as overlapping recordings is not specified.

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 output_path. The description adds little semantic value beyond restating 'new GIF path' and the start/stop actions, so the baseline score of 3 is appropriate.

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 states the exact behavior: 'Start recording to a new GIF path or stop and finalize the active recording,' with a specific resource (Playdate GIF recording). It is clear on its own, though it does not explicitly differentiate itself from siblings like playdate_capture_screenshot.

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?

The description implies usage by defining the start and stop actions, and the note that recording state belongs to the Simulator agent provides relevant context for when this tool is appropriate. However, it does not explicitly state when to prefer this over sibling tools or mention any exclusions or prerequisites.

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