get_duplicate_media

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

No annotations are provided, so the description must disclose behavior. It does not state whether the operation is read-only, what it returns, whether it scans the entire project, or if it requires any selection. The name implies a getter, but that is not explicitly declared, and no additional behavioral context is given.

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 brief, but 'Premiere Pro expanded operation' is filler that does not contribute meaning. The core phrase 'get duplicate media' is essentially the name repeated. It is concise but not optimally structured or informative.

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?

Given no output schema, no annotations, and a vague description, the tool lacks context about its return value, scope, or how it relates to similar tools. This is inadequate for an agent to understand the tool's full behavior or when to invoke it among numerous siblings.

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 input schema has no defined parameters and appears to accept arbitrary properties, but context indicates zero expected parameters. Schema coverage is 100%, so no parameter documentation is required. The description adds no information about optional arguments, but with no real parameters, this is acceptable.

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 clearly states a verb ('get') and resource ('duplicate media'), making the tool's basic purpose understandable. However, it does not differentiate from sibling tools like 'consolidate_duplicates' or 'get_unused_media', and the phrase 'expanded operation' is vague and adds little clarity.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, context, or exclusions. The description simply states the action without any usage context.

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