trmnl_duplicate_playlist_item

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, and the description is consistent with them ('Changes remote state or starts work'). It adds one useful behavioral fact — the copy is placed on the same device — but says nothing about whether a new item id is created or what the endpoint returns, which matters for a non-idempotent mutation.

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?

Purpose and target are front-loaded in the first sentence, and the endpoint line is useful for traceability. The final two sentences are generic boilerplate that could be dropped without loss.

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 nested-object mutation with no output schema, the description covers what happens (copy of a plugin setting or mashup on the same device) but not the outcome — no new item identifier, no indication of playlist ordering, and no mention of the non-default `profile` parameter. Adequate but with clear gaps.

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 only 50%, and the description adds no meaning to either parameter: `path.id` is documented in the schema as 'Playlist item id', and `profile` (default profile) is never mentioned in the description. It neither compensates for the gap nor contradicts the schema, so baseline 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?

States a specific verb (duplicate) and resource (playlist item), then clarifies what is copied — the plugin setting or mashup — and where the copy lands (same device). That detail distinguishes it from siblings like trmnl_copy_plugin_setting or trmnl_add_device_playlist_item, though it never names those alternatives.

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 when-to-use guidance and no named alternative. 'Run only within the user-authorized scope' is a safety instruction, not a selection rule, so an agent must infer from the name alone whether to duplicate versus copy or re-add an item.

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