List firecracker snapshots

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds beyond that: snapshots are temporary, they carry a billing state with a free window then a per-GB keep rate, they expire, and the call requires services:read with an API key.

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 tight sentences with no waste; the purpose is front-loaded ahead of the billing and auth context. Every clause earns its place.

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, the description helpfully characterizes the returned content (billing state, expiry) and states the auth requirement. For a single-parameter read-only list against annotations that already carry the safety profile, this is nearly complete.

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%, and the single orderNo parameter is fully documented in the schema (pattern, length, examples). The description adds no parameter-level detail, so the baseline 3 applies.

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+resource ('List temporary snapshots for a Firecracker VPS service') and adds what is exposed (billing state, expiry). This distinguishes it from the generic 'list_snapshots' sibling by qualifier and content, though it never names that 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?

The description implies a read/list operation scoped to a Firecracker service order, and notes the auth scope needed. However, it gives no explicit when-to-use guidance versus list_snapshots or the create/rollback/delete_firecracker_snapshot siblings, leaving routing to inference.

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