Create snapshot

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

Goes well beyond the annotations: discloses the free window followed by per-GB billing, that snapshots do NOT auto-expire, that only one snapshot action runs at a time, that snapshot count is limited per service, and the auth requirements (services:manage + full-access API key). This is exactly the operational context annotations cannot carry.

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?

Front-loaded and readable, but the billing fact is stated twice ('Free for a short window, then billed per GB while kept' and 'after the free window it is billed per GB while kept'), which is redundant for a description of this length. The repeated cost warning costs a point on structure.

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?

Covers cost model, expiry behavior, concurrency limits, per-service caps and auth requirements, which is thorough for a mutation tool with no annotation support for those facts. It does not describe what is returned or how to track the resulting operation, a minor gap given no output schema exists.

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%, so orderNo (tenant-owned service order number, with pattern and length bounds) and the optional description are already fully documented in the schema. The description adds no additional parameter semantics, 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 (Create) and precise resource (disk snapshot of a Cloud VPS KVM/VDS service), and implicitly contrasts with the sibling read/delete tools via the 'see list_snapshots policy' and 'DELETE the snapshot' workflow. An agent can distinguish this from list_snapshots, rollback_snapshot and delete_snapshot without opening a schema.

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?

Gives explicit when-to-use guidance ('Take a snapshot before any risky or automated change') plus follow-up workflow guidance (delete once the change succeeds). It does not explicitly name a sibling alternative (e.g. rollback_snapshot) or state when NOT to snapshot, so it falls short of a 5.

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