Delete an OBS profile and automatically switch to another profile first if the target is currently active.
Removes a profile. If the current profile is chosen, it will change to a different profile first
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | Explicit confirmation required when OBS_PROTECT_DESTRUCTIVE is active | |
| profileName | Yes | Name of the profile to remove |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and does add one genuinely useful trait: removing the current profile forces a switch to a different profile first. However, it omits whether deletion is permanent, what happens to profile-specific scene collections or settings, and it never mentions the confirm/OBS_PROTECT_DESTRUCTIVE safeguard that exists in the schema.
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 short sentences with zero redundancy, and the destructive side effect is stated immediately after the core action rather than buried. Nothing needs to be trimmed.
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, unannotated mutation tool with no output schema, the description is only partially complete: it covers the current-profile side effect but leaves irreversibility, the protection/confirm flow, and post-deletion state unexplained. It is adequate to call the tool but thin for a destructive 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 100%, with both profileName and confirm documented in the schema itself, so the baseline is 3. The description adds no meaning about parameter usage—notably it says nothing about when confirm becomes required or how profileName resolution handles unknown names.
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 ('Removes') and resource ('a profile'), so the operation is unambiguous. It does not explicitly contrast itself with siblings like obs-create-profile or obs-set-current-profile, but the name plus verb make the target obvious.
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?
There is no when-to-use guidance, no prerequisites, and no reference to alternatives such as obs-create-profile or obs-get-profile-list for verification before deletion. The only guidance is an implied behavioral note about the current profile, not a selection criterion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.