get_mogrt_media

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

With no annotations, the description must carry behavioral context. It discloses what data is returned (media slots and underlying images), which is useful, but it does not explicitly state read-only behavior, required permissions, or source-selection requirements.

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 a single dense sentence with no wasted wording, and the core resource is front-loaded. The parentheticals are functional, though the fragment style is slightly less readable.

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?

The description identifies the source modes and return content, which is important for a 5-parameter tool with no annotations or output schema. It still leaves gaps around parameter combinations, optionality, and the shape of returned media-slot data.

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 description adds meaning for the undocumented trackIndex + clipIndex pair and names the three source modes (.mogrt, library graphic, timeline clip). However, with only 60% schema description coverage, it does not fully clarify how graphic, library, and mogrtPath combine or whether one source set is required.

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 clearly identifies the resource: replaceable media slots and the images behind them for an After Effects .mogrt, library graphic, or timeline template clip. It distinguishes the resource from siblings like get_mogrt_properties or replace_mogrt_media by focusing on media slots, though it does not explicitly name those siblings.

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?

It gives no guidance on when to use this tool versus alternatives such as replace_mogrt_media, get_mogrt_properties, or list_library_graphics. Usage is only implied by the tool name and resource description.

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