manage_snapshots

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

No annotations provided, so description carries full burden. It discloses three actions but does not describe behavioral traits such as required permissions, error conditions, state changes, or the effect of missing the optional snapshot_id parameter. This leaves significant gaps.

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?

Extremely concise (11 words), front-loads the key verb and resource, and includes a colon to list actions. Every word earns its place with no redundancy.

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?

Despite having a simple schema (2 parameters, 1 required) and an output schema, the description does not explain the role of snapshot_id across actions, nor does it clarify behavior when snapshot_id is null. Sibling tools are numerous but the description does not help differentiate beyond purpose.

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 description must compensate. It adds meaning for the action parameter by listing enum values, but provides no information about the snapshot_id parameter, its purpose, or when it is required.

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 the tool manages btrfs home snapshots and lists three specific actions (list, status, diff), providing a specific verb-resource combination that distinguishes it from sibling tools like storage_diagnostics or system_doctor.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage when snapshot management is needed, but doesn't explain when to prefer it over other tools or when not to use it.

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