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

The description adds substantial detail beyond the annotations: it names what is destroyed (channels, queues, API keys, stored content), states irreversibility, notes immediate API key invalidation, and specifies the required `projects:write` permission.

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 well structured and front-loaded: purpose, scope of deletion, irreversibility, API key impact, then permission. The opening phrase repeats the tool name, which is a minor redundancy but does not hurt comprehension.

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 destructive deletion tool with no output schema, the description covers the critical behavioral consequences and permission requirement. The main remaining gap is the lack of explicit parameter guidance for the nested project ID.

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?

With only one required nested `request.id` parameter and reported schema description coverage at 0%, the description does not explain the project ID argument or the nested request shape. It relies on the resource name alone to imply the 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 starts with a specific verb and resource: 'Delete a project.' It clearly distinguishes this destructive operation from siblings like projects-update, projects-duplicate, and projects-create.

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 gives clear context for when this operation applies and emphasizes that it cannot be undone. It does not explicitly compare against alternatives such as projects-update, but the destructive purpose is unambiguous.

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