Set Offline

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

Annotations already declare the operation is not read-only, not destructive, not open-world, and not idempotent. The description adds that false refreshes an existing offline item, but does not disclose permissions, side effects, or idempotency behavior beyond what annotations and schema already provide.

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 a single front-loaded sentence that says what the tool does and covers both boolean modes without 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?

For a simple two-parameter mutation tool with an output schema and rich annotations, the description is nearly sufficient. It explains both offline and online modes, though it does not explicitly restate the default offline=true behavior that the schema provides.

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 description coverage is 100%, so item_id and offline are already well documented, including the default true and false-refresh behavior. The description restates the false case but adds no format, syntax, or semantic detail beyond the schema.

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: setting a project item offline, with an inverse online-refresh behavior. This clearly distinguishes the tool from media-inspection siblings, but it does not explicitly name alternative tools such as check_offline_media or refresh_media.

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 provides an implied usage condition by explaining that offline=false asks Premiere to refresh an existing offline item back online. However, it gives no explicit when-to-use guidance or alternatives relative to siblings like check_offline_media or relink_media.

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