get_mogrt_properties

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

With no annotations, the description carries the full disclosure burden, and it only hints at return content (property kinds). It says nothing about error behavior for non-MOGRT clips, whether values are raw or display-formatted, or whether read access has any preconditions.

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?

A single short fragment with no wasted words, but it is so terse that it omits the identifying inputs entirely. Brevity here is closer to under-specification than to disciplined concision.

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?

No output schema and no annotations, yet the description only gestures at the returned properties and never explains how the clip is targeted. For a two-required-parameter lookup tool, key information an agent needs before calling is missing.

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?

Schema description coverage is 0% and the description does not mention trackIndex or clipIndex at all, leaving both required identifiers completely undefined in prose. The description therefore fails to compensate for the schema gap.

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?

Names a specific resource (editable properties of a Motion Graphics template clip) and enumerates the property kinds (text, colors, sliders, checkboxes), which separates it from siblings like set_mogrt_property and get_mogrt_media. It is a noun phrase rather than a verb, so the 'get' semantics come only from the tool name, but the resource is unambiguous.

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?

No statement of when to call this versus set_mogrt_property (the mutator) or get_mogrt_media (media retrieval), and no prerequisites such as the clip actually being a MOGRT. The agent must infer the workflow from the name alone.

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