Delete a video

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

Annotations already declare destructiveHint=true, but the description adds what the annotations cannot: the deletion is permanent and irreversible, it also removes underlying files, it is plan-gated, and human confirmation is mandatory beforehand. That is materially more than the boolean flags convey.

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 plan gate, then the action, then the safety workflow. Nothing is wasted, and the most consequential constraint (irreversibility) appears before the call instructions.

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 two-parameter tool with no output schema, the description covers everything needed to call it safely: access gating, the sibling tool to check first, permanence, and the confirmation sequence. No meaningful gap remains.

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 the schema already documents both parameters; the baseline would be 3. The description adds genuine workflow meaning beyond the schema by specifying that confirmation must cover the exact video identified by title and link, and that videoId has no default for a delete.

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 ('Permanently delete a video and its files from recordful.app'), plus the scope of what is removed (the video and its files). An agent can immediately tell this apart from update_video or list_videos without opening the 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?

Gives an explicit precondition ('Recordful Pro only (check get_status recorder.account.plan first)') and names the sibling tool to call for that check. It also spells out the required workflow ordering: get user confirmation of the exact video, then call with confirm: true.

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