Pause briefly to let iPhone animations settle before capturing the next screenshot.
Pause, to let an animation settle before the next screenshot.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "iphone_wait"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| ms | No | Default 500; maximum 10000. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the disclosure burden. It reveals the intent behind the delay (letting animations settle) and the schema caps the sleep at 10000ms, but it doesn't say the call blocks execution for the full duration or what happens on an omitted value beyond the schema's own default note.
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?
One short sentence, front-loaded with the action and justified by purpose. Nothing redundant or padded.
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-optional-parameter timing tool with no output schema and no annotations, this is nearly enough: the purpose and a usage trigger are both present. A brief note on blocking behavior would close the remaining gap.
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 coverage is 100% and the single `ms` parameter already documents its default of 500 and maximum of 10000 in the schema itself. The description adds no format, unit, or tuning guidance beyond that, 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?
The description names a specific action (pause) and its intended effect (let an animation settle), and ties it to the screenshot workflow. It distinguishes itself implicitly from siblings like iphone_tap or iphone_swipe by being the timing primitive, though it doesn't say so directly.
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?
"before the next screenshot" gives a clear condition for when to call it, which is exactly the situation an agent needs. It stops short of stating when not to use it (e.g. between non-visual actions) or naming alternatives, so it isn't a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.