Deactivate a specific license instance using the license key and instance ID. No API key needed—the license key authenticates the request.
Deactivate a license key instance. Does not require an API key — uses the license key itself for auth.
| Name | Required | Description | Default |
|---|---|---|---|
| instanceId | Yes | The instance ID to deactivate | |
| licenseKey | Yes | The license key |
Changes observed during successful MCP inspections.
v0.10.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-read-only, non-destructive, idempotent, and open-world. The description adds the authentication behavior, but does not elaborate on other behavioral traits like reversibility or return format.
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 two sentences, front-loaded with the action, and includes a key additional detail without any fluff.
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 straightforward deactivation tool with no output schema, the description is adequate. It covers the action and a notable auth trait, but lacks details on success/failure responses.
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 description does not add meaning beyond what the schema already provides for the parameters.
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 clearly states the action ('Deactivate a license key instance') with a specific verb and resource. It distinguishes from sibling tools like ls_activate_license and ls_validate_license.
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 provides a hint about authentication (no API key needed) but does not explicitly state when to use this tool versus alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.