iaas_get_machine_snapshot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds the REST path and the parent-child scoping (snapshot belongs to a machine), but says nothing about return shape or behavior when the snapshot does not exist.

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?

Three short lines, front-loaded with the verb and resource. The endpoint line is useful context for engineers; the rest is minimal with no filler, though the first and second lines are slightly redundant.

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 read-only getter with full schema coverage and annotations declaring the safety profile, the definition is complete enough to call correctly. Minor gap: no description of the returned snapshot object, but that is expected for a straightforward GET.

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% (id, snapshotId, apiVersion all documented), so the schema carries parameter meaning. The description only restates that id and snapshotId are required, adding no format or constraint 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?

States a specific verb (Get) and resource (machine snapshot), and clarifies retrieval by snapshot id scoped to a specific machine. This implicitly distinguishes it from the list sibling iaas_get_machine_snapshots, though it never names an alternative explicitly.

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?

Usage is implied: retrieve a single snapshot when you have both a machine id and snapshot id. There is no explicit when-to-use/when-not guidance and no mention of siblings like iaas_get_machine_snapshots or iaas_delete_machine_snapshot.

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