get_offline_media

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It completely fails to describe any behavior: whether it scans the project, returns a list of items, requires any selection, or affects the state. The phrase 'expanded operation' adds no concrete information.

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 very short but under-specified. It is not concise in a helpful way; it omits essential information while adding a vague 'expanded operation' prefix. Since the name already conveys the bare resource, this single sentence does not earn its place.

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 highly generic description, the tool is completely incomplete for an AI agent to know what it does or what it returns. The context from siblings (e.g., 'check_offline_media') hints at a related operation, but the description itself offers no context.

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 required parameters and the schema shows no defined properties, so the description does not need to explain parameter semantics. Baseline for 0 params is 4, and there is no missing param information to compensate.

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' is essentially a restatement of the tool name with a generic prefix. It fails to specify what 'get offline media' means — does it return a list, check status, or something else? It does not distinguish from siblings 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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of conditions, use cases, or exclusions compared to sibling tools such as 'check_offline_media' or 'get_unused_media'.

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