get_track_info

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Premiere Pro expanded operation: get track info,' which reveals nothing about side effects, return value, or operational context. Even the read-only nature is only implied by the verb 'get.'

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 text is short but not usefully concise; the phrase 'Premiere Pro expanded operation' is filler and the rest duplicates the tool name. This is under-specification rather than disciplined conciseness.

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, an empty input schema, and no sibling differentiation, the description is severely incomplete. An agent has no way to know what 'track info' means, what the result looks like, or how this differs from many related tools.

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, so there is no parameter schema burden for the description to compensate for. However, the description adds no information about implicit context such as whether it operates on the active sequence or a named track.

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 merely restates the tool name with the meaningless prefix 'Premiere Pro expanded operation.' It identifies 'track info' as the resource but does not specify what kind of track, in what context, or what information is returned, and it does not distinguish this from siblings like get_full_sequence_info, list_sequence_tracks, or get_timeline_summary.

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 the many sequence-, track-, and timeline-related siblings. There is no mention of prerequisites, active sequence context, or scenarios where an alternative would be better.

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