VPS_deletePublicKeyV1

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

With no annotations provided, the description carries full burden. It explicitly states the key behavioral trait: 'Deleting public key from account does not remove it from virtual machine.' This is critical for an agent to understand side effects. No contradictions.

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 short sentences plus a bolded warning, all front-loaded. Every sentence adds value: purpose, critical behavioral note, and usage advice. No extraneous text.

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 parameter and no output schema, the description is nearly complete. It covers purpose, critical behavioral detail, and usage scenario. It could mention error cases or confirmation but is adequate.

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 input schema has 100% coverage with description 'Public Key ID.' The tool description does not add further meaning about the parameter beyond the schema. Baseline score of 3 is appropriate.

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 'Delete a public key from your account' with a specific verb and resource. It also distinguishes from sibling tools like VPS_createPublicKeyV1 and VPS_attachPublicKeyV1 by noting it removes unused keys from account.

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 says 'Use this endpoint to remove unused SSH keys from account,' providing clear usage context. It also warns that deletion does not remove from VM, implying when not to use (if key is still attached). However, no explicit alternative tool is named.

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