get_clip_properties

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

No annotations are provided, so the description carries the burden. It usefully discloses output specifics (normalized and pixel position values, sequence frame size, no need to export a frame) and implies a read-only operation with 'Gets'. However, it does not describe the full set of returned properties, error behavior, or sequence fallback semantics beyond the sequenceId note.

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?

Three focused sentences, front-loaded with the core purpose, followed by high-value formatting detail and a practical invocation note. No fluff or redundant restating of the schema.

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 output schema, the description partially compensates by specifying the notable motion.position return format. It is adequate for a simple read tool with two well-documented parameters, though it leaves the full 'detailed properties' scope implicit.

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 coverage is 100% with both parameters documented, so baseline is 3. The description adds valuable context beyond the schema by explaining when and why to pass sequenceId for non-active sequences and how the position output is presented.

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 uses a specific verb and resource ('Gets detailed properties of a clip') and clearly calls out the distinctive Motion values (opacity/scale/rotation/position), which differentiates it from sibling tools like get_clip_effects or get_full_clip_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?

Provides clear targeted usage guidance: pass sequenceId when the clip ID came from list_sequence_tracks for a non-active sequence. It does not explicitly name alternatives or exclusions, but the context is sufficient for correct invocation.

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