archive_videos

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

The description states 'Archived videos are hidden but not deleted,' which implies a non-destructive operation. However, the annotation destructiveHint: true indicates the opposite, creating a direct contradiction. No other behavioral traits are disclosed.

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?

The description is extremely concise with two sentences, each adding value: first states the action, second clarifies the effect. No wasted words.

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?

While the description covers the basic action and effect, the contradiction with destructiveHint undermines completeness. The output schema exists but the description does not clarify return behavior. For a tool with contradictory annotations, more context is needed.

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 baseline is 3. The description does not add any parameter-specific details beyond what the schema already provides, such as format or constraints.

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 clearly states the tool's purpose: archive or unarchive Loom videos, with a specific verb and resource. It distinguishes itself from sibling tools like delete_video by noting that videos are hidden but not deleted.

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 implies when to use: to hide videos from view without deleting them. However, it does not explicitly mention when not to use or provide alternatives among the many siblings.

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