remove_docsetDelete a locally cached docset by slug to free storage. Provide the docset slug to remove it from the cache.
Delete a docset from the local cache.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Docset slug, e.g. 'vite'. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates the destructive action and the specific scope ('local cache'), but it does not state whether deletion is permanent, what happens for a missing slug, or whether any side effects occur for dependent features like search or read.
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 wasted words. It is front-loaded with the core action and includes the useful 'local cache' qualifier without redundancy.
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 tool is simple and has one well-documented parameter, so the description is minimally viable. However, with no annotations and no output schema, an agent would benefit from more detail about result/error behavior and reversibility, making the definition adequate but not fully complete.
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%, and the schema already fully documents the single 'slug' parameter with an example. The description adds no additional parameter meaning beyond what the schema provides, 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?
The description states a clear verb ('Delete') and a clear resource ('a docset from the local cache'), making the action unambiguous. It also distinguishes this tool from siblings like install_docset and list_docsets by focusing specifically on cache deletion.
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 gives no guidance about when to use this tool versus alternatives such as install_docset or list_docsets. It also does not mention prerequisites, such as the docset needing to already exist in the local cache, or when deletion might be inappropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.