snapshot_integrity_check

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the exact validation semantics (JSON parsing, _meta key presence, track_count matching), which is substantive. But it does not state whether the check mutates anything, what happens when validation fails, or what the return shape is.

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?

The core behavior is front-loaded and compact. The appended 'Snapshot guide' is slightly run-on and not strictly necessary, but it is short and genuinely useful for navigating the large sibling toolset.

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?

Reasonable for a simple read-only validation tool, but with no annotations and no output schema the description leaves return value, failure behavior, and side-effect status implied. The snapshot tool guide helps, but it does not fully substitute for explicit guidance.

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 coverage is 100%, and both parameters already have descriptions in the schema. The tool description reinforces that snapshot can be one or all and clarifies the validation focus, but it adds little meaning beyond what the schema already provides.

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?

Describes a specific validation action ('Validate one snapshot (or all of them)') with concrete checks: JSON parses, required _meta keys exist, and track_count matches the tracks array. It is clearly distinct from create/list/read/diff/restore tools, though it does not explicitly distinguish itself from the sibling snapshot_integrity_report.

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 implied by 'Validate...' and the embedded snapshot guide that maps create/list/read/diff/restore actions to their tools. However, it never states when to prefer this tool over snapshot_integrity_report or other validation/report siblings, and gives no exclusion criteria.

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