get_duplicate_media

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

No annotations are present, so the description carries the full burden of behavioral disclosure, but it discloses nothing beyond the tool name. It does not state whether the operation is read-only, what project scope it scans, whether it can be expensive, or what the result represents.

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 it is under-specified rather than genuinely concise. The phrase 'Premiere Pro expanded operation' is filler, and the rest simply repeats the tool name without adding useful structure or information.

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?

This tool has no output schema, no annotations, an empty input schema, and a description that only restates its name. In a list of about 200 sibling tools, this leaves the agent unable to understand what duplicate media means, where the tool looks, or what it will return.

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 parameters, so there are no undocumented parameters that the description must compensate for. The description adds no parameter detail, but with a parameter count of 0, the baseline of 4 is appropriate.

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 is essentially a restatement of the tool name: 'get duplicate media' plus the boilerplate prefix 'Premiere Pro expanded operation'. It does not define what counts as duplicate media or distinguish this tool from related siblings such as get_unused_media, get_used_media_report, or consolidate_duplicates.

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 given about when to use this tool or when to prefer one of the many related siblings. There is no use case, no exclusion, and no selection rule, so the agent must guess when this tool is the right choice.

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