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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds real context beyond them: newest-first ordering, a hard cap of 50 snapshots per roadmap, and the fact that restore cannot be done through the API. The only gap is what happens when a roadmap has no snapshots (empty list vs. error).

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 short sentences, front-loaded with the returned fields and ending with the operationally important limit and the restore restriction. No filler or repeated information.

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?

There is no output schema, and the description compensates by enumerating the returned fields (id, name, note, author, timestamp, item count), the sort order, and the result cap. For a one-parameter read tool this covers everything an agent needs before calling it.

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?

With a single parameter at 100% schema description coverage, the schema already documents roadmapId fully. The description only implies the roadmap scoping through the possessive phrase and adds no format, source, or constraint detail beyond the schema, so 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?

The description names the specific resource ('A roadmap's manual snapshots (saved copies)') and its ordering, plus the exact fields returned, so an agent knows this is a metadata listing rather than a diff or restore. It stops short of explicitly contrasting itself with snapshot-adjacent siblings, so it is clear but not fully differentiated.

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 only implied by the resource and by the note that restoring a snapshot is app-only, which usefully rules out an expected follow-up action. There is no explicit statement of when to call this versus alternatives (e.g., a diff-style tool), and no prerequisites beyond the required roadmap id.

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