trmnl_resync_device_mirror

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

Annotations already declare write, non-idempotent, non-destructive, open-world. The description adds real behavioral detail beyond that: the operation is incremental (only items added since last sync) and only playlist items are propagated automatically, which is exactly the kind of scope disclosure an agent needs. It does not address re-run behavior or failure handling.

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 is front-loaded in the first line, followed by the incremental-copy caveat and the API route. The phrasing 'Only playlist items are copied automatically otherwise' is awkward/duplicative, and the final 'Run only within the user-authorized scope' line is boilerplate, but there is no serious padding.

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 non-idempotent, open-world mutation with no output schema, the description omits what happens on repeated resyncs (duplicate items?) and what the response/state looks like afterward. It covers purpose and timing well but leaves the agent guessing about the consequences of calling it more than once.

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 50% and both properties carry their own descriptions ('Device id', 'Configured profile name; defaults to default.'). The description only echoes the device_id via the URL template and says nothing about how 'profile' selects a configuration, so it adds little beyond the schema. Baseline 3 applies.

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 and resource ('Resync a mirrored device with its master') and immediately narrows the scope to 'copies playlist items the master has added since the device last synced'. That distinguishes it from broad-copy siblings like trmnl_copy_device_playlist, though it never names those siblings explicitly.

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?

Gives a concrete trigger: 'use this after adding new content to the master'. It also implicitly excludes a full playlist copy by saying only items added since the last sync are transferred. No explicit when-not condition or named alternative, so it stops short of a 5.

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