get_track_info

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

With no annotations at all, the description carries the full burden of behavioral disclosure. It fails to state whether the operation is read-only, what data it returns, whether it requires an active sequence, or any potential side effects. The description merely names the action without explaining its behavior.

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 extremely concise (six words), which is positive, but it lacks genuine structure or elaboration. The template 'Premiere Pro expanded operation:' feels generic and does not inform. It is brief yet under-specified, earning an average score.

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 and no parameter descriptions, the tool description must explain what 'track info' means and what the return value looks like. It does neither. An agent has no idea what to expect from the tool's output or how to interpret the result, making it severely incomplete.

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 parameters, and the input schema is an empty object. Given the 0-parameter baseline of 4, the description is not required to explain parameter details. It adds no parameter information, but none is needed.

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 track info,' is essentially a restatement of the tool name with a product prefix. It does not specify what 'track info' includes (e.g., track type, name, visibility) or the scope (current sequence, all tracks). It also does not distinguish this from sibling tools like list_sequence_tracks or get_sequence_structure, which likely provide similar information.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions. The phrase 'expanded operation' hints at a broader scope but offers no concrete direction, leaving the agent without any decision-making basis.

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