uninstall_plugin

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

Beyond the destructiveHint/readOnlyHint annotations, it discloses the refusal conditions (external and pro plugins), the 404 on absent IDs, and critically that the change is persisted to the database but applied later by the scheduler, so the tool cannot confirm the plugin is actually gone. That deferred-effect warning is the kind of context annotations cannot express.

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 the action and its constraints, then usage routing, then behavior. Dense but every clause carries information; the semicolon-chained sentences are slightly packed but not wasteful.

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 single-parameter destructive tool with no output schema, the description covers prerequisites, failure modes, deferred application, and the limitation that liveness cannot be verified. Nothing an agent needs in order to call it correctly 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 coverage is 100% and the parameter description already says the ID comes from list_plugins type=ui, so the description mostly repeats structured data. It adds only the constraint that the ID must refer to a UI plugin, which is useful but marginal.

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 and resource (uninstall one plugin) plus a scope restriction: only UI-installed plugins, with external and pro plugins refused. An agent can distinguish this from install_plugins and list_plugins without opening any schema.

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?

Explicitly routes to list_plugins type=ui for obtaining IDs and to install_plugins for adding a plugin, including the prerequisite 'uninstall first to replace'. It also states the exclusion (external/pro plugins are refused), so both when-to-use and when-not-to-use are covered.

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