get_offline_media

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

With no annotations provided, the description carries the full burden of behavioral disclosure and fails entirely. It doesn't state whether this is a read-only query, whether side effects occur, whether an open project is assumed, or what triggers the 'offline' state. For an operation that presumably queries or modifies project media linkage state, this is a significant transparency failure.

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?

At eight words, the description is brief, but this reads as under-specification rather than deliberate conciseness. The opening clause 'Premiere Pro expanded operation:' is filler that could be removed with zero information loss, highlighting that the entire description is just the tool name.

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 must explain both behavior and return value, and it does neither. The agent cannot determine if the tool returns a list of offline items, a count, a boolean, or triggers a UI dialog — especially ambiguous given the presence of similarly-purposed siblings like `get_used_media_report` and `check_offline_media`. This is completely inadequate for an agent to select it correctly.

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?

Per rubric, 0 parameters sets a baseline of 4, since there are no schema semantics for the description to elaborate on. The schema coverage is 100%, so there are no undocumented parameters for the description to compensate for. No deduction needed here.

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: get offline media' merely restates the tool name with underscores replaced by spaces. The phrase 'expanded operation' is opaque jargon that adds no semantic content, and no clarification is given about what 'offline' means in this context. This borders on a tautology, adding almost nothing beyond the tool's own name.

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 provides no guidance, explicit or implied, on when to use this tool versus alternatives. Given the extensive sibling list including `check_offline_media`, `refresh_media`, `relink_media`, and `set_offline`, the absence of any differentiation or usage context is a critical gap. There is no indication of prerequisites, alternatives, or exclusions.

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