consolidate_duplicates

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

With no annotations, the description carries the full burden and does not say whether this mutates or deletes media, whether it is reversible, what 'consolidate' does to the surviving copy, or what permissions are needed. For a zero-param operation with an implied destructive effect, this is a meaningful gap.

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?

A single short sentence with no filler, so it is concise and front-loaded. However, the brevity reflects under-specification rather than tight editing — the one sentence omits everything an agent needs beyond the topic.

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?

No output schema, no annotations, and no scope statement: the description never says which project (active?), what counts as a duplicate, or what the result looks like. For an operation with real media-management consequences, the definition is too thin to call safely.

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 zero properties, so there is nothing for the description to elaborate on. Baseline 4 applies; no parameter-level information is missing.

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?

Names a verb ('Consolidate') and a resource ('duplicate media in the project'), so the general domain is identifiable. But 'consolidate' is ambiguous — it could mean merge, deduplicate, relink, or delete — and the description does nothing to distinguish it from siblings like relink_media or delete_project_items.

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 indication of when an agent should reach for this tool versus relink_media, refresh_media, or delete_project_items. There are no preconditions, no exclusions, and no alternatives named despite a large sibling set touching the same media.

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