deleteApp

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. However, it only says 'Delete an app.' with no mention of permanence, irreversibility, side effects on associated resources, or any operational nuances. This adds zero information beyond the tool name itself.

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 extremely short, which avoids verbosity, but it is under-specified to the point of being unhelpful. It lacks essential details such as parameter roles, consequences, or usage guidance. This is not appropriately sized for the complexity of the operation.

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?

Given that this is a destructive delete operation with two parameters and no annotations, the description is critically incomplete. It does not describe side effects, required parameters, return behavior (though an output schema exists), or any operational warnings. The description needs substantial expansion to be 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 description coverage is 0%, and the description does not mention or explain either parameter (app_handle, account_handle). The optional account_handle's purpose (likely scoping to a specific account) is completely unaddressed. The description fails to compensate for the complete lack of schema-level documentation.

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 ('Delete') and the resource ('an app'). It is specific enough to distinguish from other resource-specific tools like deleteDatabase and deleteVhost, though it does not explicitly differentiate itself from any alternative delete tool or clarify the exact scope of deletion.

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 no guidance on when to use this tool, what prerequisites exist (e.g., required permissions), or how it compares to alternative operations. It simply restates the tool's name without adding context about appropriate usage scenarios.

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