set_offline

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

With no annotations, the description carries the full burden of behavioral disclosure. It states only that something is 'set offline' without explaining side effects, reversibility, whether it acts on selected items, or any other behavioral implications. This is severely under-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?

While the description is short, it is under-specified rather than concise. The single sentence adds no operational or contextual value, and it does not earn its place in the description.

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 tool with no defined parameters and no output schema, the description must at least clarify the target of the operation (e.g., selected clips, project items). It fails to do so, leaving the tool's behavior entirely ambiguous and contextually incomplete.

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?

The input schema defines no properties (parameter count 0), so the description is not responsible for documenting parameters. According to the baseline for zero-parameter tools, this dimension is adequately handled by the schema itself.

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 'Premiere Pro expanded operation: set offline' largely restates the tool name and does not specify what object is being set offline (clips, project items, media) or the resulting behavior. It fails to distinguish the tool from related siblings like check_offline_media or get_offline_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?

No guidance is given about when to use this tool versus alternatives, nor are prerequisites or the required context (e.g., selection state) mentioned. The phrase 'expanded operation' is unhelpful and does not clarify usage.

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