gesture

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

No annotations are provided, so the description carries full burden. It mentions the action ('perform gesture') but doesn't disclose behavioral traits like whether this requires a running simulator, what happens if the gesture fails, or if there are side effects. The description is minimal and doesn't provide context about execution environment or error conditions.

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, efficient sentence that front-loads the core action ('perform gesture') and lists all preset options without unnecessary words. Every element earns its place by specifying the target (iOS simulator) and available gestures.

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?

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the preset options and target environment, but lacks details on behavioral context, error handling, or integration with sibling tools, leaving gaps for an agent to infer usage.

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 high (88%), so the baseline is 3. The description lists the preset gesture options, which matches the 'preset' parameter's enum values in the schema, but doesn't add meaning beyond what the schema already provides for other parameters like 'delta', 'duration', or 'simulatorUuid'.

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 clearly states the verb ('perform') and resource ('gesture on iOS simulator') with specific scope ('using preset gestures'). It distinguishes from sibling tools like 'swipe' and 'tap' by specifying it uses preset gestures rather than custom coordinates or durations.

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 context (iOS simulator testing) but doesn't explicitly state when to use this tool versus alternatives like 'swipe' or 'tap'. It lists the available preset gestures, which suggests usage for standardized gestures, but lacks explicit guidance on prerequisites or when-not-to-use scenarios.

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