quest_clear_data

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

The description discloses that the tool resets an app to freshly-installed state and mentions specific data types (saves, settings, caches). However, it does not explicitly state that data is permanently deleted, cannot be recovered, or note any permissions required, which is significant for a destructive operation without annotations.

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 two concise sentences, with the action and scope in the first sentence and a use case in the second. No wasted 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?

For a destructive tool with no annotations and no output schema, the description leaves important gaps: no warning about data loss permanence, no mention of what response to expect, and no parameter guidance. The provided use case is helpful but does not fully cover operational context.

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 schema description coverage is 0%, and the description does not mention the parameters package_name or device_id. It does not explain how to specify the app or the optional device, leaving parameter semantics entirely to the user.

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 clear verb 'Clear' and specifies the resource 'an app's data', with an additional clarifying phrase 'resets it to freshly-installed state'. This distinguishes it from sibling tools like quest_install or quest_uninstall, which have different actions.

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 provides a concrete use case: 'Useful for wiping test state (saves, settings, caches)'. This signals when the tool should be used, though it does not explicitly state when not to use it or name alternatives.

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