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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that — result ordering (newest first) and that each entry carries its contents — but says nothing about volume, pagination, or retention limits, which matters for a listing tool.

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?

A single compact sentence with the ordering constraint and payload hint front-loaded and no filler. It is telegraphic to the point of being slightly clipped, which costs it the top score.

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 list with full schema coverage and no output schema, the description is adequate but thin: it does not say whether results are paginated, how many snapshots come back, or how this relates to the 'snapshot' and 'rollback' siblings that operate on the same objects.

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?

Only one parameter (server) with 100% schema description coverage, including the 'optional when the account has one server' nuance. The description's phrase 'on the server' loosely ties to that parameter but adds no format or default information beyond the schema, so the baseline of 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?

Names the resource (snapshots) and its scope (on the server) plus the ordering (newest first) and rough return content (what each holds). It is a noun phrase rather than a verb phrase, so the 'list' action comes from the title, and it does not distinguish itself from the singular sibling 'snapshot' (likely the create/rollback side).

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?

No statement of when to list snapshots versus using 'snapshot', 'rollback', or 'list_servers'. The only usage-adjacent detail is in the schema ('Optional when the account has one server'), not in the description, so an agent gets no routing guidance.

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