models_delete

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

Annotations already declare `destructiveHint: true`, and the description explicitly mentions deletion. It adds the behavioral detail that the model can be identified either by ID or by slug+project, which helps the agent understand supported identification methods beyond what annotations provide.

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 a single, clear sentence with no unnecessary words or repetition. It is optimally concise for the tool's simplicity.

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?

Considering the simple nature of a delete operation and the presence of `destructiveHint` annotation, the description covers the essential identification methods. It does not explain return behavior or side effects, but for a destructive action with no output schema, it is adequate.

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 documentation coverage is 100%, and the description largely mirrors the schema's parameter descriptions. It concisely restates the two identification modes but does not add new semantic details beyond the schema, warranting a baseline score of 3.

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 ('Delete'), the resource ('a model'), and the two identification methods ('by id, or by slug plus project'). It distinctly differentiates from sibling tools like `models_get` and `models_list` by specifying the deletion action.

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?

No explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or conditions. The usage is implied by the action 'Delete' but lacks context such as 'when you need to remove a model permanently' or 'use models_get to verify before deletion'.

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