Delete a project

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

No annotations are provided, so the description carries full burden. It discloses permanent deletion, absence of trash/undo, the confirmation requirement, and the refusal behavior when confirmName does not match—all critical behavioral traits for a destructive operation.

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?

Two concise sentences front-load the action and essential safety constraints. Every word earns its place, with no irrelevant detail.

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?

The tool has no output schema or annotations, but the description covers purpose, safety, and parameter usage thoroughly. It could mention what happens on success (e.g., confirmation message), but the provided information is sufficient for safe invocation.

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 documents confirmName but not projectId (50% coverage). The description adds meaningful context for confirmName (exact current name, mismatch refusal) and clarifies the deletion target, partially compensating for the missing projectId description.

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 begins with 'Permanently delete a Claude Design project or design system', a specific verb and resource. The title and sibling tools (delete_chat, delete_files) further distinguish it, making the tool's purpose unmistakable.

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 explicitly instructs to ask the user before calling and explains the confirmName safeguard. It provides clear context for when to use the tool but does not mention alternative tools or when not to use it beyond the user-permission requirement.

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