semrush_delete_project

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

Annotations already indicate destructiveHint=true, so the agent knows this is a destructive operation. However, the description adds no further behavioral context, such as whether deletion is permanent, requires specific permissions, or affects associated data.

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 five words, which is appropriate for a simple tool. However, the conciseness comes at the cost of missing essential information, making it barely adequate.

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 tool with one parameter and no output schema, the description lacks critical context: how to obtain the project_id, what happens on deletion, any side effects, and error scenarios. The agent is left with insufficient information to use the tool safely.

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 description does not explain the 'project_id' parameter beyond its schema definition (number, >0). With 0% schema description coverage, the description fails to clarify how to obtain a valid project_id or what format it expects.

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 a Semrush project'. The verb 'Delete' and resource 'project' are specific. Among sibling tools like create_project, update_project, get_project, list_projects, the purpose is well-distinguished.

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, nor any prerequisites or conditions for deletion. The agent receives no context about project ownership, dependencies, or recovery options.

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