delete_project

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

No annotations are provided, so the description carries the full behavioral burden for a destructive mutation. It never states that deletion is irreversible, what cascades (issues, pipelines, members) are removed, or what permissions are required; the only trait it mentions, the confirmation requirement, is already documented in the schema's confirm_project_name parameter.

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?

A single sentence that front-loads the verb and resource with no filler. It is efficient, though the brevity is partly what leaves behavioral gaps unaddressed.

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?

With no annotations, no output schema, and a destructive operation, the definition is only marginally complete. The parameters are well covered by the schema, but an agent gets no signal about irreversibility, permission requirements, or side effects.

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 description coverage is 100%, so both parameters are fully documented in the schema itself, including the ID/namespace formats and the confirmation-matching rule. The description adds no meaning beyond that, meriting the baseline 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?

States a specific verb and resource ("Delete a project/repository") that unambiguously identifies the operation and separates it from siblings like delete_branch or delete_project_variable. There is no competing sibling over the same resource, so no explicit differentiation is needed, but it also makes no reference to alternatives.

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 parenthetical notes a prerequisite (explicit name confirmation), which implies a safety-gated usage context. However, it gives no when-to-use vs when-not guidance and does not point the agent to alternatives such as update_project or archiving.

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