ios.capture_screenshot

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states the core action and output destination, but it does not mention return value, failure conditions, side effects, or how the artifact is stored/named. This is minimally adequate but not rich.

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 one efficient sentence with no filler. It front-loads the action and destination, which is ideal for conciseness.

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 simple capture tool the core operation is clear, but the definition lacks parameter explanations, prerequisites, and return/artifact details. Since there are no annotations and no output schema, the description is not complete enough for an agent to invoke it correctly with the optional parameters.

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%, and the description adds no meaning to either 'device' or 'prefix'. The agent cannot infer from the description what values these parameters expect, what a prefix affects, or whether 'device' refers to a simulator UDID, name, or something else.

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 uses a specific verb ('Capture'), a clear resource ('an iOS simulator screenshot'), and a final destination ('into artifacts'). It also differentiates from the sibling device.capture_screenshot by explicitly targeting the iOS simulator, so an agent can tell them apart.

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?

No when-to-use guidance is provided. The description does not mention prerequisites such as a booted simulator, nor does it distinguish when to use this tool over appium.observe_screen, verify.collect_evidence, or device.capture_screenshot. Usage context is only implied by the tool name.

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