app_clear_data

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

With no annotations provided, the description carries the full burden of disclosure. It explicitly states that the operation is irreversible, requires approval, and is restricted to allowlisted packages. This communicates the most critical behavioral traits, though it does not detail the exact extent of data cleared or any side effects.

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 a single concise sentence that front-loads critical qualifiers ('Approval-required irreversible') and wastes no words. Every term adds meaning.

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 two parameters and no output schema, the description covers the essential context: approval requirement, irreversibility, and package restriction. It does not mention prerequisites like whether the package must be installed, but the overall usage context is adequately complete.

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 has no descriptions (0% coverage), so the description must compensate. It mentions 'Approval-required' and 'allowlisted test package', which loosely map to the 'approved' and 'package_name' parameters, but it does not explicitly explain how to use each parameter, such as setting 'approved' to true to confirm. Partial guidance is provided.

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 tool clears local data for a specific resource (an allowlisted test package). It uses the specific verb 'clearing' and includes important qualifiers ('approval-required', 'irreversible') that distinguish it from any sibling tool.

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 implies when to use the tool (when you need to clear local data for a test package), but it does not explicitly contrast it with alternatives or state when not to use it. There is no mention of other app-related tools like app_launch or app_stop, which would help differentiate.

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