Rename a video or change who can watch

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

Annotations only say it is a non-destructive, idempotent, open-world write. The description layers on plan gating, a mandatory human-confirmation step, the permission model (recorder or workspace owner), and the default target (last recording) — none of which appear in the annotations.

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?

Front-loaded with the plan gate and confirmation protocol, which are the highest-value facts. Some space is spent re-enumerating the three visibility values that the enum schema already documents, which is the only real 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 3-parameter mutation tool with no output schema, the definition covers everything an agent needs to call it safely: entitlement check, permission requirement, confirmation gate, default video target, and allowed values. No behavioral gap remains that would cause a bad invocation.

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% and the description's visibility definitions and "defaults to the last recording" note restate the schema's own property descriptions nearly verbatim. It adds no syntax, validation, or edge-case meaning beyond the schema, so baseline 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 and resource ("Change a video's title and/or who may watch it") and enumerates the exact mutable fields. It is clearly distinguishable from siblings like delete_video, move_videos, and get_video, which touch the same resource but do different things.

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?

Gives the gating prerequisite (Recordful Pro, verify via get_status recorder.account.plan), the required confirmation flow ("Show the user exactly what you will change and wait for their yes first"), and the authorization rule. An agent knows exactly when it may and may not call this.

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