Delete app

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

With no annotations, the description carries the burden of disclosing destructive behavior. It does say 'permanently delete' and 'and its data', conveying irreversibility and scope. However, the confirm requirement is already documented in the schema's confirm parameter description, so this adds no new information. No other behavioral traits (e.g., cascading effects, permission requirements) are disclosed.

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?

A single sentence that efficiently communicates the core action and the critical prerequisite. No filler or redundant phrasing; every word earns its place.

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 covers the essential destructive nature and confirmation requirement but omits details like how the app is identified, whether deletion is reversible (though 'permanently' implies it), and any side effects on related resources. Given the low complexity (2 params, no nested objects), it is adequate but not thorough.

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 description coverage is only 50% (confirm is described; app is not). The description mentions only the confirm requirement (redundant with schema) and provides no clarification on what the 'app' parameter should be (e.g., app ID, name, path). This leaves the agent without guidance for the 'app' parameter, which is a significant gap.

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?

States a specific verb ('delete') and resource ('an app and its data'), clearly distinguishing it from siblings like delete_file. The 'app' noun makes the target unambiguous, though it does not explicitly name the alternative tool for 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?

Provides a prerequisite ('requires confirm=true') but no explicit guidance on when to use this tool versus alternatives. It does not mention any context where delete_app is preferred or excluded, leaving the agent to infer based on the tool name alone.

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