get_clip_markers

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

With no annotations, the description carries the full burden of disclosing behavior, but it says nothing about what the returned marker data includes, whether selection affects results, or if this is a read-only operation. The description adds no behavioral traits beyond the fact that it gets clip markers.

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 sentence, but it is under-specified rather than concise; it adds no information beyond the tool name. The phrase 'Premiere Pro expanded operation' is filler and does not earn its place.

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 tool has no annotations, no output schema, and a generic schema with no defined parameters. Given the existence of many marker-related sibling tools, the description is far too minimal. It does not clarify what 'clip markers' includes, how results are returned, or what the tool's scope is.

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 schema has zero defined parameters and no description; the context confirms 0 parameters. Since there are no parameters to clarify, the description does not need to add parameter semantics. Baseline for 0 params is 4.

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 clip markers' merely restates the tool name with a generic prefix. It does not provide a specific verb-resource statement beyond the name, nor does it distinguish from sibling tools like get_sequence_markers_by_type or list_markers.

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 guidance is provided on when to use this tool versus alternatives. The phrase 'expanded operation' is vague and does not indicate context such as whether to use it for clip markers vs sequence markers or how it differs from list_markers.

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