uninstall_app

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

With no annotations provided, the description must fully convey behavioral traits. It clearly states that the tool removes/ uninstalls an app, which communicates destructiveness. However, it does not disclose side effects, whether the action is reversible, or if any confirmation/permission is required. The core behavior is transparent, but some safety details are missing.

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 two short sentences. The first sentence front-loads the primary purpose, and the second provides essential usage guidance. No wasted words.

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 simple 1-parameter tool with no output schema, the description adequately covers the action, scope, and how to obtain the required id. It could mention the return value or effects after uninstall, but that is not essential for this straightforward operation.

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 100% and the parameter description already states 'App subscription id (from list_apps / get_app)'. The description adds the minor detail that the 'id' field from list_apps should be used, but this is largely redundant with the schema. The added value is small, so a 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 uses the specific verb 'Uninstall (remove)' and clearly identifies the resource as 'an installed application from the current site.' It is immediately distinguishable from sibling tools like install_app, update_app, and get_app.

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 clear context for when to use the tool (to remove an installed app) and gives a prerequisite: obtain the subscription id from list_apps or get_app. It does not explicitly mention when not to use it or alternative tools, but the context is sufficient for this straightforward destructive operation.

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