list_snapshots

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

No annotations are provided, so the description must disclose behavioral traits. It mentions timeout risks but omits details like read-only nature, pagination, default behavior when dataset is null, or response format. The description is insufficient for full transparency.

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 description consists of two focused sentences with no extraneous information. The first sentence states the purpose, and the second provides a key usage tip. It is efficiently front-loaded.

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?

Given the presence of an output schema, the description does not need to explain return values. However, it lacks context on prerequisites, error conditions, or behavior when dataset is not specified (beyond timeout). The single usage tip helps but leaves gaps for a complete understanding.

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 input schema has 0% description coverage for the 'dataset' parameter. The description adds meaning by stating the parameter should always be specified to avoid timeouts, implying it is optional but recommended. This provides some semantics beyond the schema, but lacks format or allowed values.

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 'List ZFS snapshots,' which is a specific verb and resource. It distinguishes this tool from sibling list_* tools like list_datasets and list_snapshot_tasks by naming the exact resource type.

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 advises to 'Always specify a dataset to avoid timeouts on large systems,' providing clear when-to-use guidance. It does not explicitly mention when not to use or alternatives, but the advice is actionable and relevant.

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