trmnl_uninstall_app

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false. The description adds useful behavioral context by stating that calendars, fleet memberships, and device bindings are also removed, and it warns that remote state changes and authorization scope matter.

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 short, front-loaded with the action, and then gives effects, endpoint, and a safety note. The line "Changes remote state or starts work" is slightly generic, but overall the structure is efficient.

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 mutation with rich annotations and no output schema, the description covers the essential impact and authorization warning. It does not explain the optional profile parameter or expected response, but the annotations and schema already carry much of that burden.

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 50% and both the nested installation id and optional profile parameter have schema descriptions. The description reinforces that the id is the installation identifier via the DELETE endpoint, but it adds no meaning for the profile parameter beyond what the schema already provides.

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 gives a specific verb and resource ("Uninstall an app") and explains that it retires an installation. It does not explicitly distinguish this from nearby siblings such as trmnl_cancel_installation or trmnl_install_app, so it is clear but not fully differentiated.

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 implies the tool removes an installation, but it does not say when to use it versus alternatives like trmnl_cancel_installation or trmnl_delete_device_association. The only usage constraint is a generic authorization warning, not selection guidance.

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