appium_app_lifecycle

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

Annotations only declare readOnlyHint=false and openWorldHint=true. The description does not disclose that several actions are destructive (uninstall, clear), that a confirmToken workflow gates repeats, that some actions require id/name, or that inputs resolve on a remote Appium server. For a mutation-heavy tool, this leaves most behavioral burden undocumented in the description text.

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?

It is a single, front-loaded sentence with no filler, which is structurally clean. But the brevity comes from under-specification rather than efficient communication; the sentence reads as a topic list rather than an actionable definition.

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?

This is a 13-parameter, 10-action mutation tool with no output schema and minimal annotations. The description omits confirmation requirements, destructive-action warnings, required-parameter distinctions per action, and session scoping, leaving it far from complete for the complexity involved.

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 100%, so the schema already explains id, path, action semantics, seconds, confirmToken, and other parameters in detail. The description adds no parameter meaning beyond the generic topics "state, data, and deep links," so it sits at the baseline for fully documented schemas.

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?

"Manage app lifecycle, installation, state, data, and deep links" correctly signals a multi-action app-management tool and enumerates the domains covered. However, "Manage" is a vague umbrella verb, and the description never differentiates this tool from siblings such as appium_session_management or appium_mobile_device_control, so the agent must inspect the action enum to know what it actually does.

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 gives no when-to-use guidance, no alternatives, and no exclusions. All routing information (which action to pick, when confirmation is required, when to use this versus session tools) lives in the schema's action description, not in the tool description itself.

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