marketplace_uninstall

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

With no annotations, the description carries the full burden. It usefully discloses the confirmation gate beyond what the schema shows (confirm defaults to false), which is genuine behavioral context for a destructive operation. However, it says nothing about irreversibility, what data is removed, permission/role requirements, or why admin_password exists.

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 terse sentences with zero padding; the action and the safety precondition are both stated up front with no wasted words.

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?

An output schema exists, so return values need no explanation, but for a destructive, unannotated tool the definition omits the effects of uninstalling, the role of admin_password, and any recovery story. It is under-specified for the risk profile of the operation.

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 must compensate for all three parameters. It only clarifies confirm (that it must be true) and leaves admin_password entirely unexplained and module undocumented beyond the tool name, despite admin_password being a meaningful optional input for a privileged uninstall.

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 specific verb (uninstall) and resource (marketplace module) in a single front-loaded sentence. It is inherently distinguishable from siblings like marketplace_deploy, marketplace_list, and marketplace_call, though it does not explicitly name a boundary against them.

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?

Provides one concrete precondition ("Requires confirm=true"), which tells the agent how to invoke it safely, but gives no when-to-use vs. when-not guidance and never mentions alternatives or the sibling tools that manage the same modules.

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