Delete app

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the action is permanent and reversible (implies destructive), and requires confirm=true for safety. It also indicates app data is deleted. This is sufficient transparency for a delete operation, though it doesn't elaborate on permissions or 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 the core action and the critical requirement. No unnecessary words or redundancy.

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 provides the essential fact (permanent deletion) and a safety requirement, but leaves gaps: the 'app' parameter is unspecified, and there is no indication of return values or failure behavior. For a destructive tool with no annotations, more context would be helpful, though it is minimally viable.

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 coverage is 50%: only 'confirm' has a description. The tool description adds no clarification for the 'app' parameter, leaving its expected format (e.g., ID or name) undefined. The requirement 'confirm=true' reinforces the schema but does not compensate for the missing app semantics.

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 clear verb ('Permanently delete') and resource ('an app and its data'), making the tool's purpose unambiguous. It also differentiates from the sibling delete_file by specifying that it targets apps, not files.

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 usage (when you need to remove an app) but does not explicitly contrast with alternatives like delete_file or specify conditions for choosing this tool. It mentions the confirm requirement, but no when-to-use or when-not-to-use guidance is given.

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