deleteProject

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

Annotations only declare readOnlyHint=false, indicating mutation, but the description adds nothing about the consequences of deletion (e.g., irreversibility, cascading deletions, access requirements). Since there is no destructiveHint annotation, the description carries the full burden of disclosure, and it fails to provide any behavioral context beyond what the name already implies.

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 extremely short, but this is under-specification rather than effective conciseness. It provides no structure or front-loaded information that aids agent comprehension. Every useful detail is absent, so the brevity does not serve a purpose.

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 destructive operation with nested parameters and no output schema, this description is wholly inadequate. It lacks any mention of effects on related resources, required permissions, or return values. The agent has no guidance beyond the minimal schema, making the tool very difficult to use correctly.

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 0%, meaning the description must compensate for the lack of parameter documentation. However, the description mentions no parameters at all. It does not explain the purpose of pathParams, the format enum, or projectId, leaving the agent to infer them solely from the schema structure and property names.

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 'Delete project' is essentially a restatement of the tool name 'deleteProject' with no additional specificity. It identifies the resource but does not elaborate on scope, cascade behavior, or any details that would distinguish it from other delete tools beyond the name itself. This falls into the tautology category.

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 no guidance on when to use this tool versus alternatives. It does not mention any preconditions, alternatives like closeProject or archiveProject, or circumstances that would make this the appropriate choice. An agent would have to infer usage entirely from the name and schema.

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