delete_registered_model

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

Annotations already indicate the tool is destructive. The description adds context: 'Irreversible — all versions, aliases, and tags are permanently removed,' which explains the scope of destruction beyond the annotations. However, it does not mention error behavior or permissions.

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 very concise: two sentences for purpose and behavior, plus a brief parameter doc. It is front-loaded with the main action and irreversible nature, with no redundant information.

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 simple deletion tool with one parameter and no output schema, the description covers the key aspects: what is deleted, irreversibility, and what is affected. It could mention error handling for non-existent models, but overall it is complete enough.

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%, so the description must compensate. The parameter 'name' is explained as 'Name of the registered model to delete,' which provides meaningful context beyond the schema's type string. This is sufficient for a single string parameter.

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 'Delete an entire registered model and all its versions' with a specific verb and resource, distinguishing it from sibling tools like delete_model_version (only a single version) and delete_model_alias (only an alias).

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 usage for complete removal, but does not explicitly state when not to use or suggest alternatives (e.g., delete_model_version for a single version). The destructive hint in annotations is clear, but guidance is minimal.

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