get_mogrt_component

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 does not state whether this is a read-only operation, whether it requires an active Premiere Pro project, what side effects might occur, or what the return value represents. The description is nearly empty of behavioral 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 short, but the phrase 'expanded operation' is unhelpful filler and the rest simply mirrors the tool name. It is under-specified rather than efficiently written, and no useful information is front-loaded because none is provided.

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 vague one-line description, an agent has almost no context for correctly invoking this tool. It does not explain what a mogrt component is, how the tool knows which component to retrieve, what the result looks like, or whether any project state is required. This is far from complete for safe and correct use.

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 declared parameters, so the baseline is 4. Although the schema allows additional properties, the description adds nothing about any optional parameters, but with no required inputs there is little to explain. The lack of parameter documentation is not a significant gap for invocation.

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 is essentially a restatement of the tool name: 'get mogrt component.' The phrase 'Premiere Pro expanded operation' adds only a vague product context and does not clarify what a 'mogrt component' is or what specific data is retrieved. It fails to distinguish this tool from related tools like import_mogrt or get_clip_properties.

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 on when to use this tool versus alternatives. The description gives no context about prerequisites, active selections, or what situation would call for retrieving a mogrt component. An agent would have to guess based on the tool name alone.

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