deleteProject

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

No annotations exist, so the description must carry the full burden. It only says 'Delete project' with no disclosure of destructive/irreversible effects, cascading deletions, permissions, or associated data impact.

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?

At two words, the description is minimal but not usefully concise—it restates the tool name without adding structure or detail. Under-specification is penalized here, not rewarded, as it fails to communicate necessary context.

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?

Given a destructive operation with a nested parameter object and no annotations or output schema, a two-word description is grossly inadequate. It lacks effects, return behavior, authorization requirements, or parameter meaning.

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%; the nested pathParams object with format and projectId is entirely undocumented in the description. The description does not explain these parameters or the format enum's role.

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' merely restates the tool name (deleteProject) and provides no additional detail. It does not differentiate from sibling project lifecycle tools like closeProject or archiveProject, and lacks any nuance about scope or permanence.

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?

No guidance is provided about when to use this tool versus alternatives such as archiveProject, closeProject, or deleteUser. There is no mention of prerequisites, workflow, or exclusions.

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