VPS_deletePublicKeyV1

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

With no annotations, the description carries the burden of behavioral disclosure. It adds a critical, non-obvious behavior: 'Deleting public key from account does not remove it from virtual machine.' This goes beyond the schema and helps the agent understand the tool's actual effect.

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 very concise, with only two sentences and a bold emphasis line. Every sentence adds value: one defines the action, the next warns about the VM not being affected, and the last states the usage case. No wasted words.

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 deletion tool with one parameter and no output schema, the description covers the essential purpose, the unique behavioral nuance, and the intended use case. It is complete for the agent to select and invoke correctly.

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 one parameter with a description ('Public Key ID'). The tool description does not add any additional meaning to the parameter. With 100% schema coverage, a 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 it deletes a public key from the account, and the bold note distinguishes it from sibling tools by clarifying that deleting from account does not remove from VM. The verb 'Delete' and resource 'public key' are specific and unambiguous.

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 explicitly says 'Use this endpoint to remove unused SSH keys from account,' which gives a clear when-to-use context. It does not explicitly exclude other scenarios, but the sibling tools (e.g., VPS_getPublicKeysV1, VPS_attachPublicKeyV1) provide implicit differentiation.

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