Uninstall App (ADMIN)

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

The description discloses the destructive cascade behavior ('Cascades: removes its widgets from all pages') which is critical behavioral context. Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the description's cascade detail meaningfully adds value beyond annotations without contradicting them.

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 compact, information-dense sentences with zero waste. Every clause adds value: the action, the permission requirement, and the cascading consequence.

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?

The annotation set is rich (destructive, non-idempotent, non-readonly), and the description covers the permission gate and cascade behavior well. No output schema means return format guidance would help, but for a straightforward uninstall action the description covers the critical risk factors. The dryRun parameter remains unexplained.

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 0%, so the description carries the full burden for explaining parameters. It explains appKey context implicitly (the app being uninstalled) and the ADMIN key requirement, but it does not explain the dryRun parameter at all, which is a notable gap for a destructive tool where dry-run testing would be valuable.

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 the action ('Uninstall an app from the workspace') with a specific verb+resource, and even notes it 'Cascades: removes its widgets from all pages.' It does not explicitly differentiate from sibling tools like kilango_deactivate_app_in_portal (which likely deactivates rather than uninstalls), so it misses top marks but is clear about intent.

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 notes 'Requires an ADMIN key' which signals a permission prerequisite. However, it does not explicitly say when to use this vs alternatives like deactivate_app_in_portal or delete_connection. The cascading-destructive nature is implied as a warning, offering partial guidance.

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