aem_bundle_uninstall

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It identifies the action as 'Uninstall,' implying a destructive operation, but does not disclose side effects, reversibility, required permissions, or the effect on other bundles.

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 a single short sentence with no fluff and puts the action and resource up front. It is concise, though slightly under-specified; the brevity is a positive structural trait even if behavioral details are missing.

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 tool with no annotations and no output schema, the description lacks important context: it does not clarify how an agent should identify the target (bundleId vs symbolicName), how instances are selected (aliases vs instances), or what a successful uninstall returns.

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?

The schema already provides descriptions for all four parameters (100% coverage), so the baseline is 3. The description adds no extra meaning about the parameters, such as how aliases and instances relate or whether bundleId and symbolicName are alternatives.

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 a specific verb ('Uninstall') and a specific resource ('OSGi bundles on AEM instances'), making the tool's action unmistakable. It also stands apart from sibling tools such as aem_bundle_start, aem_bundle_stop, and aem_bundle_refresh because the operation is clearly uninstallation, not lifecycle state change.

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 states what the tool does but not when it should be chosen over alternatives. It never mentions, for example, that aem_bundle_stop or aem_bundle_restart should be preferred for temporary changes, so an agent receives no decision guidance.

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