Revoke an alias like 'champion' from a registered model, leaving the model version unchanged. Manage promotion labels cleanly.
Remove an alias from a registered model (e.g. revoke 'champion'). The alias is permanently removed; the model version itself is not affected.
Args: name: Name of the registered model. alias: Alias to remove, e.g. 'champion', 'production'.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| alias | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate destructiveHint=true, and the description confirms the alias is permanently removed but the model version is not affected. This adds useful context beyond annotations without contradiction.
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 sentences plus an Args block, front-loaded with the main action. Every sentence is necessary and informative.
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?
Given the low complexity (2 required params, no output schema), the description covers the effect, usage, and parameter meaning completely. No gaps.
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 0%, but the description explains both parameters: 'name' as 'Name of the registered model' and 'alias' as 'Alias to remove, e.g. champion, production'. This compensates for missing schema descriptions.
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 'Remove an alias from a registered model' with examples like 'revoke champion'. It distinguishes from sibling tools by specifying it only removes the alias, not the model version.
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 implies when to use (to revoke an alias) and provides parameter guidance in the Args block. It does not explicitly mention when not to use or compare to alternatives, but it is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.