delete_project

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

With no annotations, the description must disclose behavioral traits on its own, but it fails to mention whether deletion is permanent, cascading, or permission-restricted. For a destructive operation, this lack of transparency is a serious safety gap.

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 concise at three words, but this brevity sacrifices essential detail. It is not a well-structured, informative description; it is minimal and under-specified, balancing brevity against completeness.

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 delete operation with no output schema and no annotations, the description is grossly incomplete. An agent lacks information about side effects, reversibility, or prerequisites, making it unsafe to invoke autonomously.

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 covers 50% of parameters (workspace_id has a description), but the required 'id' parameter is not described, and the tool description adds no parameter meaning whatsoever. An agent cannot infer that 'id' refers to the project ID or what workspace_id does beyond the schema's minimal 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 clearly states the action (delete) and the target resource (project), using a specific verb and noun that distinguish it from create_project, update_project, and delete operations on other entities like squads or issues.

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 on when to use this tool versus alternatives, nor any prerequisites, exclusions, or consequences such as whether deleting a project affects associated issues or members. The description simply says 'Delete a project.' with no contextual direction.

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