trmnl_stop_mirroring_device

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's value-add is scope clarification: it names exactly what is destroyed (the mirror link) and what survives (device playlist history), plus the underlying HTTP route. It stops short of stating permission requirements or the response shape.

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?

Front-loaded with the scope statement and the destructive-vs-safe distinction in the first two lines; no wasted prose. The trailing 'Changes remote state or starts work. Run only within the user-authorized scope' is generic boilerplate that adds little.

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 destructive mutation with no output schema, the description supplies the crucial blast-radius information and the endpoint. Remaining gaps (auth/permission requirements, error behavior, whether the call succeeds if no mirror exists) are modest given the annotations already flag destructiveness and idempotency.

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%: device_id and profile both carry descriptions in the schema. The description's endpoint template reinforces that device_id is a path parameter but adds no meaning for the 'profile' selector or any format constraints, so it neither compensates for nor worsens the partial coverage.

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+resource ('Stop mirroring / Clears the device's mirror') and preempts the most likely misreading by clarifying that the DELETE targets the mirror link, not the device with its playlist history. An agent can distinguish this from sibling mirror/resync operations without opening the schema.

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 when-to-use guidance relative to the obvious siblings (trmnl_mirror_device, trmnl_resync_device_mirror) and no prerequisites stated. The only directive, 'Run only within the user-authorized scope,' is generic safety boilerplate rather than a selection condition.

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