ReaMCP

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

No annotations provided, so the description carries the full burden. It fails to disclose where the duplicated item appears (immediately after the original? at the play cursor?), whether the original remains selected, or if the operation is undoable. 'Duplicate' implies mutation but specifics are absent.

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 of six words is appropriately front-loaded with the action and object. However, given the lack of schema documentation and annotations, extreme breveness here contributes to under-specification rather than efficient communication.

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?

Output schema exists (covering return values), and the operation is conceptually simple. However, with zero parameter schema coverage and no annotations, the description should have elaborated on parameter semantics and placement behavior to be fully complete.

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?

Schema coverage is 0% - neither track_index nor item_index have descriptions. The description mentions 'media item' and 'track' which conceptually map to the parameters, but provides no explanation of what these indices represent (0-based vs 1-based), valid ranges, or how they identify the specific item.

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?

Clear verb 'Duplicate' and resource 'media item'. The phrase 'on its track' distinguishes it from sibling tools like duplicate_track and duplicate_time_range, though it could clarify whether the duplicate remains on the same track or is placed elsewhere.

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 provided on when to use this versus duplicate_track, duplicate_time_range, or copy-paste workflows. No prerequisites or constraints mentioned (e.g., whether the item must be selected first).

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