sylve_zfs_dataset

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds nothing on top — no statement that `delete` is irreversible, whether snapshots/children are affected, or that creation requires a node or context. For a tool spanning read and destructive write paths, the description contributes no behavioral context beyond the annotation.

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?

A single front-loaded sentence with no wasted words, which is good structurally. However the brevity is under-specification rather than economy, given nine parameters and five actions.

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 nine-parameter, five-action tool with a nested `properties` object and no output schema, one sentence is inadequate. An agent cannot tell from the description what `properties` accepts on edit, what delete removes, or how node vs cluster-wide scope interacts with each action.

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 78%, so the schema carries most parameter meaning and the baseline applies. The description adds zero parameter detail — notably nothing about `properties`, the nested object that is entirely undocumented, and nothing clarifying `edit` semantics.

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?

States a specific verb set (list/create/edit/delete) against a specific resource (ZFS filesystems and volumes), which cleanly separates it from siblings sylve_zfs_pool and sylve_zfs_snapshot. What it omits is that all five operations are multiplexed through a single `action` parameter rather than being distinct calls.

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?

There is no guidance on when to choose this tool over sylve_zfs_pool or sylve_zfs_snapshot, no prerequisite or permission notes, and no hint about which action value suits which situation. The five enum values are listed only in the schema, with no routing advice.

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