phone_longpress

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

No annotations are provided, so the description carries the full burden. It discloses experimental status and runtime prerequisites, which is useful, but does not explain side effects, failure behavior, waiting semantics, return values, or permission constraints.

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 three short sentences with no wasted text. The experimental warning is front-loaded, followed by prerequisites and the core action, making it easy to scan.

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 three-parameter gesture tool with no annotations and no output schema, the description covers the action and dependencies but leaves important gaps: coordinate system, default duration, return/error behavior, and interaction side effects.

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 0%, so the description must compensate. It identifies x and y as coordinates and duration as optional seconds, but leaves coordinate origin/units, valid ranges, and the default duration unspecified, and it does not address why no parameters are marked required.

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 specific verb and target: 'Long-press at {x, y}' with an optional duration. This clearly identifies a phone gesture action. It does not explicitly contrast with siblings like phone_tap or phone_swipe, so it falls short of full sibling differentiation.

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 tool's usage is implied by the gesture name and the prerequisite context ('Needs iPhone Mirroring and a python3 with pyobjc'). However, there is no explicit guidance on when to choose long-press versus phone_tap, phone_swipe, or other alternatives.

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