consolidate_duplicates

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

No annotations provided, so the description must disclose behavioral traits. It doesn't explain whether this operation is destructive (deleting duplicates), requires user confirmation, what criteria define duplicates, or what the impact on project references is. The verb 'consolidates' is vague and could imply copying or merging without deletion.

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?

Single sentence, minimal waste. Would benefit from clarifying the operational scope (e.g., deletes duplicates or relinks) but no unnecessary words.

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?

For a zero-parameter tool that performs a potentially complex operation, the description lacks critical information about the consolidation logic (criteria for duplicates), results (deleted items? logs?), and whether it's reversible. The existence of get_duplicate_media suggests there is a detection step that could be mentioned.

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 schema coverage is 100% (empty schema). Since no parameters exist, the description is not expected to add parameter semantics. Baseline for 0 params is 4, and the description doesn't introduce inconsistencies.

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 states that the tool consolidates duplicate media items, a clear action on a specific resource. However, it doesn't differentiate from the sibling tool consolidate_and_transfer, which likely handles similar operations with additional transfer functionality.

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 like consolidate_and_transfer or get_duplicate_media. The context of consolidation (e.g., for project cleanup, saving space) is implied but not explicitly stated.

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