Delete Post-Install Script

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

The annotation declares destructiveHint=true, and the description's 'Delete' is consistent with this. However, the description adds no additional behavioral context beyond the annotation, such as irreversibility or effects on associated resources.

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 a single concise sentence, 'Delete a post-install script.', which is front-loaded and free of filler.

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 simple delete operation with one required parameter and a destructiveHint annotation, the description is adequate but minimal. It does not mention return values or error states, though the simplicity of the operation makes this less critical.

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 already documents script_id as a required number with description 'Script ID', achieving 100% coverage. The description adds no further parameter meaning or usage details.

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 the specific verb 'Delete' and identifies the resource as 'post-install script', clearly distinguishing it from sibling tools like vps_scripts_create, vps_scripts_update, and vps_scripts_list.

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 provides no explicit alternatives or when-to-use guidance. It relies on the tool name and the delete operation to imply usage, but does not mention prerequisites or scenarios where deletion is appropriate versus other script operations.

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