Get VPS Snapshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Get snapshot details,' which implies a read operation but does not disclose what happens, what is returned, authentication requirements, or any side effects. There is no additional behavioral context beyond the verb 'Get.'

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 sentence, but it is under-specified rather than concise. It lacks essential details about what 'snapshot details' means or how the vm_id is used. While it is short, it does not earn its place by providing useful information beyond the title.

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?

With no output schema and no description of return values, the tool is incomplete for an agent to understand what it will receive. The simplicity of the tool (one parameter) mitigates the gap, but the ambiguity about whether multiple snapshots are returned and the lack of any output description leaves significant room for improvement.

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, vm_id, with 100% schema description coverage ('Virtual machine ID'). The description adds no extra meaning to this parameter or its relationship to snapshots. Baseline 3 is appropriate because the schema already fully documents the parameter, but the description does not enrich it.

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 'Get snapshot details' clearly indicates a read operation for snapshot information, with a specific verb and resource. It distinguishes from sibling tools like vps_create_snapshot, vps_restore_snapshot, and vps_delete_snapshot. However, it doesn't clarify whether it retrieves all snapshots for a VM or a single snapshot, which is ambiguous given the only parameter is vm_id.

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 guidance on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or references to sibling tools. It lacks any context such as 'Use this to view snapshot details for a VM' or 'For managing snapshots, see vps_create_snapshot/restore/delete.'

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