set_offline

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it fails entirely. 'set offline' implies a state-changing mutation, but nothing is stated about its scope (all media vs. selection), reversibility, prerequisites, or side effects. For an unannotated mutation tool, this is empty.

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 short, but this is under-specification rather than conciseness — it repeats the tool name almost verbatim with no informative content. The 'Premiere Pro expanded operation' prefix adds no useful signal and nothing is front-loaded beyond the tautology.

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?

With no output schema and no annotations, the description is the only source of context, and it is a tautology. An agent cannot determine the operation's effect, target, prerequisites, or return value. This is completely inadequate for safe 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?

The tool has zero declared parameters and the input schema is an empty object, so there is nothing for the description to add; the baseline of 4 applies. One minor caveat is that additionalProperties:true technically permits arbitrary fields, which the description neither confirms nor clarifies.

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 reads 'Premiere Pro expanded operation: set offline.', which essentially restates the tool name with a generic boilerplate prefix. No specific verb or resource is defined — an agent cannot tell what 'offline' refers to (media, clips, effects) or what the operation actually does. This is a tautology.

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?

There is zero guidance about when to use this tool versus any alternative. The sibling set includes check_offline_media, get_offline_media, and relink_media, but the description never distinguishes among detection, listing, or recovery workflows. An agent receives no routing information.

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