Preview removing folder items

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds the crucial 'preview' trait, telling the agent this does not actually mutate state, which is real value beyond annotations. It stops short of explaining what the preview produces or that a commit follow-up is needed.

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 zero filler. The operation and its scope are stated immediately with no wasted words.

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?

An output schema exists so return values need not be explained, and annotations cover safety. However, with 0% param coverage and no usage guidance, the absence of any note on the preview/commit workflow leaves this thin for a stateful dry-run operation.

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 the load. It does add a little by tying the call to 'playlist or folder TRNs', implicitly explaining item_type's domain and that item_trns are TRN strings, but it omits TRN format, the 1-500 item bounds, and which parameter 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?

States a specific verb+resource ('Preview removing') and scope ('from the collection tree'), and matches the item_type enum by naming 'playlist or folder TRNs'. It does not explicitly distinguish itself from the commit sibling or the other preview_remove_* tools, but the folder-scoped resource makes it identifiable.

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 indication of when to use this versus the non-preview remove operations or when to follow with a commit. There is no mention of prerequisites, dry-run semantics, or alternative tools, leaving usage entirely to inference.

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