delete_project_script

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the archiving option ('optionally archiving it first'), which is useful context for a destructive operation, but it never states whether the deletion is permanent/reversible, what archive=true actually does (move vs. copy), or what permissions are required.

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 destructive action and its scope are front-loaded in the first sentence, and the second sentence delivers routing context with no filler. Slightly verbose in the context sentence but every clause arguably earns its place for sibling disambiguation.

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?

An output schema exists so return values need no explanation, but for a destructive tool with no annotations and no parameter descriptions, the definition leaves material gaps: the meaning of the 'sync' flag and the permanence of the deletion. Adequate but not complete.

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% for four parameters, so the description must compensate. It partially does: it explains the 'archive' flag and the folder location implied by the tool, but 'sync' (default true) and the required project_name/file_name semantics are left entirely unexplained.

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 states a specific verb (delete) and a precisely scoped resource (a Lua script within a repo project's sync/ or drafts/ folder), which immediately separates it from delete_script and delete_directory_script. An agent can identify the target of the operation without opening the schema.

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?

It gives clear routing guidance: repo project folders are 'local organization helpers,' and for active Roblox Code Sync the agent should use directory project tools plus sync_directory/connect_sync. This names an alternative and the condition that selects it, though it doesn't explicitly cover the sibling delete_script/delete_directory_script distinction.

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