get_target_tracks

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

The description gives no behavioral detail beyond the operation name. It does not disclose what data is returned, whether it is read-only, or any side effects. With no annotations available, this leaves the agent entirely without transparency.

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 short, but this is under-specification rather than effective conciseness. It simply restates the tool name with no additional context, failing to 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 is a getter with no parameters, but the description still fails to explain what target tracks are or what the return value represents. Given the rich context of sibling tools, this description is completely inadequate for an agent to understand the tool's role.

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 schema is fully descriptive for that, so the description is not required to add parameter details. The baseline of 4 for 0 parameters applies, even though the description itself adds no parameter-related meaning.

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 target tracks' is essentially a restatement of the tool name. It lacks a specific verb and resource that clarifies the operation's function, and does not distinguish it from sibling tools like set_target_track or get_track_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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or distinctions from similar sibling tools.

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