delete_model_instance

Does 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. 'Delete' implies a destructive operation, but the description does not mention irreversibility, permissions, cascading effects on versions, or whether deletion is permanent. This is a significant gap for a destructive tool.

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 short with no fluff, but it is more under-specification than purposeful conciseness. It adds little beyond the tool name and provides no structured information, so conciseness is adequate but not a strength.

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 one-parameter destructive tool with no output schema and no annotations, the description should explain the parameter, the consequences of deletion, and what the response indicates. It covers none of these, leaving the agent with only the operation's name and no operational context.

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?

The input schema has one parameter, instance_ref, with an empty description (0% schema coverage). The tool description does not compensate by explaining what instance_ref should contain, such as an ID, slug, or path. The agent receives no meaningful semantic information about the required 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 states a specific verb and object: 'Delete a model instance.' It clearly identifies the operation and distinguishes it from sibling tools like delete_model and delete_model_version. However, it does not define what a model instance is, so it is clear but not fully explanatory.

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 guidance on when to use this tool versus alternatives such as delete_model or delete_model_version. No prerequisites, exclusions, or contextual triggers are provided, so the agent must infer usage entirely from the tool name and sibling list.

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