adb_clear_data

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

The description fully discloses behavioral traits: destructive nature, irreversibility, and specific data wiped (app data, cache, databases, shared preferences, login state). Since no annotations are provided, the description carries the full burden and meets it comprehensively.

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 concise (three sentences) and front-loaded with the primary action. Every sentence adds essential information: what it does, behavioral impact, and input requirements.

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?

The description is complete for a destructive tool with no output schema. It explains the effects, required confirmation, and operational context, leaving no significant gaps for an AI agent to misuse.

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?

The input schema already covers all parameters with descriptions (100% coverage). The description adds meaning by explaining the confirm parameter's purpose and the AP5 fix to prevent accidental data loss, which goes beyond the schema's 'must equal packageName' constraint.

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 action ('Clear all data for a package') with a specific verb and resource, and provides a familiar analogy ('equivalent to clearing storage in settings'). It uniquely identifies this tool among numerous sibling tools focused on ADB operations.

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 hints at when to use (to clear app data) but does not explicitly compare with alternatives like adb_force_stop or adb_uninstall. The mention of 'DESTRUCTIVE' and the confirm requirement provides some usage context, but lacks guidance on when not to use this tool.

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