Get snapshot

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

The description's 'view' language aligns with the annotations readOnlyHint=true and destructiveHint=false, with no contradiction. It adds only the 'current' qualifier and does not disclose additional behavioral details such as not-found behavior or snapshot state requirements, though the annotations already cover the safety profile.

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?

Two short sentences with minimal waste; the first sentence states the core action and resource clearly. The second sentence is slightly redundant but brief and front-loaded enough not to harm clarity.

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 one-parameter read-only operation with readOnlyHint and destructiveHint annotations, the description is sufficient for an agent to select and invoke the tool. No output schema exists, so explaining return format is not required; the description covers what the endpoint does and the parameter is fully documented.

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 100%, with virtualMachineId already described as 'Virtual Machine ID'. The description reinforces that the snapshot corresponds to a specified virtual machine but adds no new semantic detail beyond the schema.

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 a specific verb ('Retrieve') and resource ('snapshot for a specified virtual machine'), clearly indicating a read operation. It distinguishes itself from sibling write operations like VPS_createSnapshotV1, VPS_deleteSnapshotV1, and VPS_restoreSnapshotV1 through the 'view' language.

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 phrase 'Use this endpoint to view current VPS snapshot information' gives some usage context but does not explicitly state when to choose this tool over alternatives or mention that create/delete/restore are separate operations. No exclusions or sibling comparisons are provided.

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