remove_video_from_showcase

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

Annotations already provide idempotentHint=true, destructHint=false, and readOnlyHint=false, so the bar for extra behavioral disclosure is lower. The description meaningfully adds that the video stays in the library, clarifying that only the showcase association is removed. It does not cover effects on the showcase or error behavior, but the core safety profile is well covered.

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?

Two short sentences with no filler. The first sentence states the action, and the second sentence provides the key non-destructive clarification. Every sentence earns its place and the structure is 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?

This is a simple two-parameter mutation with no output schema and no nested objects. The description plus schema adequately convey what happens, what is untouched, and what identifiers are required. No critical information is missing for an agent to invoke it correctly.

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%, with both video_id and showcase_id already described in the input schema. The tool description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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'), a specific resource ('video'), and a specific container ('showcase'). It immediately clarifies that the video itself remains in the library, distinguishing it from delete_video and delete_showcase. This is clear and unambiguous.

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 clearly implies this tool is for removing a single video's association with a showcase, and that it should not be chosen when deleting the video is intended. It does not explicitly name sibling alternatives or state when-not conditions, but the context is strong enough for correct routing.

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