VPS_getPublicKeysV1

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

With no annotations provided, the description carries the full burden. It indicates a read-only operation ('Retrieve'), but does not disclose any additional behaviors like authentication requirements, rate limits, or return format. The description is adequate but lacks extra context.

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 concise sentences. The first sentence states the purpose, and the second provides usage context. There is no unnecessary text, and every sentence adds value.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is nearly complete. It could mention that the result is a list of public keys or that pagination may be needed, but the current description is sufficient for an agent to understand basic functionality.

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 only parameter is 'page' with schema description 'Page number', and schema coverage is 100%. The description does not add any further meaning or usage guidance beyond what the schema already provides, so 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 explicitly states 'Retrieve public keys associated with your account', which is a specific verb-resource pair. It distinguishes from sibling tools like VPS_getAttachedPublicKeysV1 (which retrieves keys attached to a specific VM) and VPS_createPublicKeyV1/VPS_deletePublicKeyV1.

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 includes 'Use this endpoint to view available SSH keys for VPS authentication', providing clear context for when to use. However, it does not explicitly exclude alternatives or mention when not to use, such as when needing keys attached to a specific virtual machine.

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