restart-app

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

No annotations provided, so description carries full burden. It discloses terminating and relaunching, refreshing native-devtools injection, tvOS focus-driven interaction, return value, and failure condition. Missing potential side effects like persistence of app data, but the tool's purpose (restart) implies no data loss beyond state. Overall transparent for the operation.

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?

Four sentences, each earning its place: action, usage scenario, platform-specific behavior, outcome/failure. Front-loaded with main purpose. No unnecessary words.

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?

No output schema, but description specifies return format '{restarted, bundleId}', which is sufficient. Covers parameters (all in schema) and platform specifics (tvOS vs iOS). Could mention that app data persists, but not required for basic understanding. Complete for a simple restart tool.

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%, so baseline is 3. Description adds context like 'udid' from 'list-devices' and notes 'activity' is Android-only, which is already in schema. No additional semantics beyond schema that significantly aid selection.

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?

Description clearly states the verb 'Terminate then relaunch' and the resource 'app by bundle id / package name'. It distinguishes from sibling tools like 'reinstall-app' by noting 'without a full reinstall' and from 'launch-app' by implying a restart rather than fresh launch. Also mentions tvOS-specific behavior, differentiating from other tools.

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?

Explicitly says 'Use when you need a clean in-memory state without a full reinstall', providing when-to-use guidance. Also advises on tvOS to use 'tv-* tools rather than coordinate taps', which is an exclusion. States failure condition 'Fails if the app is not installed'.

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