delete_model

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

With no annotations provided, the description fully discloses the critical behavioral aspects: it cascades to delete all records and causes permanent deletion. It also explicitly states the requirement for user confirmation. This is a strong disclosure of side effects and safety requirements, exceeding what is typically expected.

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 concise sentence followed by a warning. The warning is front-loaded, making the destructive nature immediately apparent. Every word earns its place; there is no unnecessary fluff or repetition.

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 delete operation with one parameter and no output schema, the description covers all essential context: the action, the cascading effect, the permanence, and the need for user confirmation. An agent has enough information to invoke the tool safely and appropriately.

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 schema already describes the only parameter (idOrSlug) with 'The model's id or slug to delete.' Since schema description coverage is 100%, the description adds no additional meaning beyond what the schema provides. The baseline of 3 applies because the schema carries the full documentation burden.

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 a data model.' This is a specific verb plus resource, and it distinguishes itself from sibling tools like delete_record and delete_page by naming the resource type. It is not a tautology and provides immediate understanding of what the tool does.

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 provides clear context for when the tool should be used: only after explicit user confirmation. It warns about the cascading destructive effect, which implies it should not be used casually. However, it does not explicitly mention alternatives or when not to use it, such as when only a record should be deleted instead of the whole model.

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