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

Annotations already declare read-only/idempotent/non-destructive, yet the description still adds real behavior: bodies are excluded from results, labels and forum posts are quoted untrusted data, and prompt-injection instructions must not be followed. That is meaningful context beyond the structured fields, though it omits ordering and pagination behavior.

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?

Purpose is front-loaded in the first sentence and the remaining sentences are short and mostly load-bearing security warnings. Minor redundancy between the 'labels' and 'forum posts' untrusted-data sentences, and the API-key warning appears without saying what to supply instead.

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?

No output schema exists, so the description should at least sketch the shape of a snapshot; it only says bodies are excluded. Pagination and result ordering are undocumented, leaving the three-parameter surface underspecified for a listing tool.

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 0%, so the description must carry parameter meaning and does not: neither 'limit' nor 'cursor' is explained, and no pagination or max-size semantics are given. 'This key's' only loosely implies api_key identifies the locker, without clarifying its role versus the model-provider key prohibition.

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?

First sentence states a specific verb and resource scoped to the caller: "List this key's locker snapshots." That distinguishes it from mutating siblings like save_state/load_state/delete_state, though it never names the closest alternative (e.g. export_state) 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 says what it lists but gives no when-to-use or when-not-to-use guidance relative to the many state/read siblings (load_state, export_state, read_since, read_threads). The only conditional language is a safety prohibition, not usage selection.

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