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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by specifying what is destroyed (media record, stored asset, and third-party provider copies) and by stating the confirmation requirement. It stops short of describing irreversibility, failure modes, or downstream effects on the node.

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?

Three short sentences, front-loaded with the action and its destructive scope, followed by the confirmation prerequisite. No filler or 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?

For a destructive tool with rich annotations and a fully documented schema but no output schema, the description covers what is deleted and the confirmation gate. It omits what the caller should expect afterward (return value, node state) and whether the deletion can be undone, which would be the final useful additions.

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 100%, including detailed guidance on the confirm flag and form_id (UUID vs share_id), so the schema carries the parameter burden. The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 3 applies.

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 ('Remove/Deletes') and resource ('media from a node') and clarifies the exact scope of deletion — the media record plus the stored asset. An agent can distinguish this from clipform_get_node_media, clipform_attach_node_media, and clipform_delete_node without opening any schema.

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 gives one prerequisite ('Requires user confirmation before it runs'), which is genuinely useful context. However, it names no alternatives or when-not-to-use conditions, and never distinguishes itself from sibling media tools like attach_node_media or delete_node explicitly.

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