apex_delete_app

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

While annotations already indicate destructiveHint=true, the description adds the critical context that the deletion is 'permanently' — meaning irreversible. This goes beyond the annotation by clarifying the permanence and lack of recovery, which is essential for a delete operation.

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, front-loaded sentence with no wasted words. It efficiently conveys the action and its key qualifier ('permanently') without 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?

Given the simple one-parameter schema, the presence of an output schema, and annotations covering destructiveness, the description is largely complete. It could be argued that more detail about side effects (e.g., deleting all associated components) is needed, but the word 'permanently' and the existing structured data suffice for a basic understanding.

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 input schema already provides a clear description for the single parameter (app_id), achieving 100% coverage. The tool description does not add additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 a specific action (delete) and resource (APEX application), with the qualifier 'permanently' reinforcing the scope. It distinguishes from sibling delete tools (e.g., apex_delete_page, apex_delete_region) by explicitly targeting the application level.

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?

No guidance is provided on when to use this tool versus alternatives, such as exporting the app first or using preview/undo tools. The description implies it's for removing an app, but there are no explicit exclusions or alternative recommendations, which is especially important for a destructive operation.

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