add_video_to_showcase

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

Annotations already indicate idempotency and non-destructiveness, but the description adds valuable context: the video stays in the library and is not moved, and the reason for the one-at-a-time design is spelled out. This goes beyond what annotations alone convey, though it doesn't address edge cases like duplicate additions or error behavior.

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 sentences deliver the core operation, a critical non-move side-effect note, and an explicit usage instruction with reasoning. Every sentence earns its place, and the most important constraint 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?

For a low-complexity tool with two straightforward parameters and supportive annotations, the description provides sufficient context: what the operation does, what it does not do, and how to call it correctly. No critical information for invoking the tool correctly is missing.

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 100% coverage with 'Video id to add' and 'Showcase id,' so the description doesn't need to explain parameters further. It adds no new semantic detail beyond the schema, matching the baseline for high schema coverage.

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 opens with 'Add one video to a showcase,' which states a specific verb, resource, and the 'one' constraint that distinguishes it from any bulk operation. It clearly differentiates from the bulk showcase endpoint and from sibling tools like add_videos_to_folder by scoping to a single video and a single showcase.

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 explicitly says 'Call this once per video' and explains why the bulk endpoint is not exposed because it replaces the whole contents rather than appending. This gives direct when-to-use and when-not-to-use guidance, leaving no ambiguity about calling frequency.

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