Delete Sideloaded Channel

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

Annotations already declare destructiveHint and idempotentHint; the description adds human-readable detail that deletion when nothing is sideloaded still results in no Dev App, and notes the password-optional behavior tied to Dev Studio's memory. This adds context beyond the structured hints without contradicting them.

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?

Three sentences: first states the main action, second covers edge behavior and password, third routes to the alternative. No filler, front-loaded with the core operation.

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 destructive, idempotent two-parameter tool with no output schema, the description covers what is removed, the empty-state behavior, password handling, and the alternative install path. An agent has everything needed to invoke it correctly.

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?

Input schema provides 100% coverage with clear descriptions for both 'device' and 'password'; the description restates password optionality but does not add new meaning beyond the schema. Therefore the baseline of 3 applies.

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 action ('Remove the currently sideloaded Dev App') and explicitly distinguishes it from the sibling 'sideload' by noting that sideload overwrites rather than requiring a delete first. This makes the tool's purpose immediately distinguishable from its closest alternative.

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 names the alternative tool (sideload) and the condition under which it should be used (install/replace), and clarifies that delete_sideload is not a prerequisite. Also explains when password is optional, giving the agent clear decision criteria.

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