Like or unlike a video

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

Beyond the annotations (readOnlyHint false, idempotentHint true, destructiveHint false), the description discloses the Pro-plan entitlement gate, that the call can remove an existing like, and that it returns the new like count. Idempotency is consistent with the annotations. It stops short of describing failure behavior when the plan check fails or the video ID is invalid.

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?

Four short, purposeful sentences with the entitlement constraint front-loaded, then the effect, then the return value, then the target default. No filler and no repetition that isn't doing work.

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 two-optional-parameter mutation with no output schema, the description covers the plan gate, side effect, return value, and default target. The remaining gap is error/entitlement failure behavior, which is minor given how simple the tool is.

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 coverage is 100%, so both parameters are already documented, including the liked toggle and the videoId source list. The description restates the liked:false semantics and the last-recording default rather than adding new meaning, 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?

The description states a specific verb and resource — 'Like a video as the signed-in user' — and immediately clarifies the inverse behavior ('liked: false removes it'). This is easily distinguished from nearby siblings like comment_on_video or update_video, which do not affect like state.

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?

It gives both a hard prerequisite ('Recordful Pro only (check get_status recorder.account.plan first)') and a default-resolution rule ('Defaults to the last recording'). It does not name alternatives or when-not-to-use cases, but the plan gate and implicit-target rule cover the main usage decisions.

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