Uninstall App

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description goes further by clarifying that uninstall removes installation state but does NOT delete stored data, that native endpoints become unavailable, and that org-admin credentials are required – exactly the kind of beyond-annotation context that matters for a destructive 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?

Front-loaded with labeled sections (Purpose, Returns, Behavior, Auth, Safety) that let an agent scan the operative facts quickly. Every section carries information the agent needs, including return values that are otherwise unavailable since no output schema exists.

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, 3-required-param mutation with no output schema, the description covers purpose, return shape, data-retention behavior, auth requirements, and a confirmation safeguard. Nothing material is missing.

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 the schema already documents organization, cluster, and appId (including provenance from list-apps/list-clusters). The description's mention of the three identifiers adds confirmation guidance but no new syntax or format detail, so the baseline of 3 applies.

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?

States a precise verb+resource: uninstall a RawTree app from one cluster and disable its native endpoints. This is clearly distinguished from the sibling install-app and from cluster-level tools like pause-cluster.

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?

Gives a clear precondition – the user must confirm organization, cluster, and app ID before calling – which implies the context of use. It stops short of explicitly contrasting with alternatives or stating when-not-to-use (e.g., pausing vs uninstalling).

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