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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond annotations: snapshot timing, ordering, row fields including _id, createdAt, replacedBy, and full playbook text. This gives the agent a solid understanding of what the operation returns and how snapshots relate to writes.

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 tightly written sentences with no filler. The primary purpose and ordering are front-loaded, followed by snapshot lifecycle context, row schema, and a pointer to the relevant sibling tool.

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 list operation, the description covers the key contextual needs: what is returned, ordering, snapshot creation timing, and the related restore tool. No output schema exists, but the row fields are enumerated. Pagination or result limits are not mentioned, though this is a minor gap for a list endpoint.

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?

The schema already provides 100% coverage for the single workspaceId parameter, including the note about user keys vs workspace keys. The description restates 'for the workspace' but does not add meaningful parameter-level 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?

The description clearly states a specific action and resource: 'List playbook version snapshots for the workspace, newest first.' It distinguishes this from related tools like campaignstack_get_playbook and campaignstack_revert_playbook by focusing on version snapshots rather than the current playbook or restoration.

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 provides clear context by explaining when snapshots are created ('before every playbook write') and routes the agent to campaignstack_revert_playbook when restoration is needed. It doesn't explicitly state when not to use this tool versus alternatives, but the context is sufficiently clear for a listing tool.

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