delete_installation

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

Annotations already set destructiveHint=true, but the description adds specific behavioral details: deletion includes rendered images and is irreversible. This goes beyond the annotation, providing useful context about the operation's scope and permanence.

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?

Two concise sentences, no fluff. The first sentence states the action and scope, the second emphasizes irreversibility. Structure is front-loaded and clear.

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 delete operation, the description covers purpose, scope (including images), and irreversibility. There is no output schema, but it's not strictly necessary for a delete. Some agents might benefit from knowing return format, but overall it's sufficiently complete.

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 100%, so parameters are already well-documented. The tool description does not add extra meaning beyond what's in the schema. It mentions 'rendered images' but that pertains to the action, not the parameters.

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?

Tool name is 'delete_installation' and description states 'Delete an app installation from a device, including its rendered images.' The verb and resource are clear, and the description adds specific scope (rendered images). This distinguishes it from siblings like 'update_installation' and 'list_installations'.

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 mentions 'This cannot be undone,' implying caution but does not explicitly state when to use this tool vs alternatives. It lacks guidance on prerequisites (e.g., need to call list_installations first) or when not to use. However, the destructive nature is clear, giving some implied usage context.

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