get_offline_media

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. It merely says 'get offline media' and 'Premiere Pro expanded operation,' without explaining whether this scans the project, returns a list, updates state, requires a connection, or has side effects. This is essentially no behavioral transparency.

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 it is under-specified rather than concise. 'Premiere Pro expanded operation: get offline media' contains almost no useful content and does not earn its place as a meaningful tool definition.

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 annotations, no output schema, and a very terse description, the definition is completely inadequate. An agent cannot determine what this tool returns, how it behaves, or when it should be used, especially given the large set of sibling media-related tools.

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 parameters and an empty schema, so the baseline is 4. The description adds no parameter information, but none is needed for a parameterless tool.

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 mostly restates the tool name ('get offline media') with a generic 'Premiere Pro expanded operation' prefix. It does not say what the tool returns or does beyond retrieving offline media, and it does not differentiate itself from sibling tools like check_offline_media or get_unused_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?

There is no guidance about when to use this tool versus alternatives. No mention of check_offline_media, relink_media, get_used_media_report, or other related operations. The agent is left to infer the intended use case.

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