delete_project

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It prominently warns that the action is permanent, cannot be undone, and that it deletes associated storage buckets and secrets—essential context beyond merely saying 'delete project'.

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 two sentences plus a warning, with no redundant wording. The warning is effectively broken out on a new line, making critical safety information prominent and easy to parse.

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?

The destructive impact (permanence, scope) is thoroughly covered, and the presence of an output schema likely handles return values. However, the complete lack of parameter explanation for neptune_json_path remains a significant gap, especially since the tool is otherwise simple.

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 sole parameter, neptune_json_path, has 0% schema description coverage and the description does not explain what it represents, its format, or how to obtain it. This leaves the agent without necessary guidance for correct invocation.

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 uses a specific verb ('Delete') with a clear resource ('a project') and scope ('all its resources'). This clearly distinguishes it from all sibling tools, which are non-destructive operations like listing, deploying, or querying.

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 clearly implies when to use this tool (when permanent deletion of a project is desired) and there is no competing delete operation among siblings. However, it does not explicitly state exclusions or alternatives, such as 'use this only if you want to permanently remove a project and its data'.

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