get_mogrt_component

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

No annotations are provided, and the description does not disclose any behavioral traits. It does not state whether this is a read-only operation, what it returns, whether it requires a specific app state, or any side effects. 'get' implies a read, but that is not made explicit.

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 (one sentence), but it is under-specified rather than concise. It offers no meaningful information, so the sentence does not earn its place. It is not as minimal as a single tautological word, but it is close to that.

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 lack of explanation about the operation's purpose, return value, or expected behavior, this description is completely inadequate for an agent to properly select and invoke the tool. The tool name suggests it retrieves a component of a motion graphics template, but nothing in the description confirms that.

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 input schema has zero defined parameters, so the description is not expected to explain any. Since there are 0 parameters, the baseline is 4 per the rubric. However, the schema's 'additionalProperties' allows arbitrary inputs, which is potentially confusing, but the description adds no misleading parameter information either.

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 mogrt component' essentially restates the tool name with a vague 'expanded operation' prefix. It does not define what a 'mogrt component' is or what the tool does with it, and it does not distinguish this from sibling tools like import_mogrt or get_project_item_info.

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 absolutely no guidance about when to use this tool versus alternatives. It does not state prerequisites, typical use cases, or exclusions, leaving the agent without any context for selecting it.

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