delete_model

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

No annotations are provided, so the description carries the full burden. The word 'permanently' does communicate irreversibility, but the description omits consequences such as whether versions or instances are also deleted, ownership requirements, or any confirmation behavior.

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 extremely short and front-loaded, containing no filler words. It is concise, but the brevity contributes to the lack of contextual guidance.

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?

Although the tool has a simple single-parameter signature, the complete absence of parameter semantics, usage guidance, and behavioral consequences beyond 'permanently' leaves an agent under-equipped to invoke this destructive tool safely and correctly.

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 only parameter, model_ref, has an empty schema description and 0% schema description coverage. The tool description adds no explanation of what model_ref should contain or its expected format, so the agent receives no meaningful parameter guidance.

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 ('Delete') and resource ('a model'), adding 'permanently' to signal irreversibility. It does not explicitly differentiate from sibling tools like delete_model_instance or delete_model_version, though the resource name is reasonably distinct.

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 about when to use this tool versus delete_model_instance, delete_model_version, or delete_dataset. The agent must infer usage entirely from the tool name and sibling context.

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