Invoke a Playdate Simulator toolbar action

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

The description discloses a real behavioral quirk: the gif action may open a Save Recording dialog. Annotations do not provide meaningful safety context beyond all-false hints, so the description carries the burden, but it only covers one action and says nothing about side effects of pause, restart, console, or others.

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 short and the behavioral caveat is front-loaded in the second sentence. The first sentence largely repeats the title, but the word 'exact' adds a small amount of precision, so the text is still efficient overall.

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 tool is simple, the action enum is in the schema, and an output schema exists, so return-value information is not required. The description covers the main gotcha (gif dialog) and directs to the right alternative. It could be more complete by flagging which actions are non-interactive or require a running simulator, but it is sufficient for most calls.

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?

The schema describes pid and provides self-explanatory enum values for action, so the schema already covers much of the parameter meaning. The description adds a useful caveat about the gif action, but it does not explain pid selection or the meaning of less obvious actions like sampler or lua-memory.

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 a clear verb and resource: 'Invoke an exact Simulator toolbar action.' It also distinguishes itself from playdate_record for GIF capture. However, it does not enumerate or otherwise clarify the specific toolbar actions beyond the schema, and it overlaps with the tool title.

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 gives an explicit when-not/alternative rule: for the gif action, use playdate_record instead to avoid the Save Recording dialog. This is useful but only addresses one of several possible actions, leaving sibling distinctions like playdate_set_paused vs. the pause action unaddressed.

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