trmnl_bulk_update_device_playlist

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the general safety profile is covered. The description adds useful nuance that hide/show is reversible visibility state rather than deletion, plus the 'user-authorized scope' caution, but it says nothing about idempotency behavior (matching idempotentHint=false) or what happens to items already in the target state.

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?

The purpose and the delete alternative are front-loaded in the first two sentences, which is the right ordering. The trailing 'Changes remote state or starts work / user-authorized scope' lines are generic boilerplate that adds little for this specific tool.

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-body mutation tool with no output schema, the description covers intent and the delete exclusions but leaves the agent without return-value expectations, partial-failure semantics across a batch, or idempotency behavior. Annotations carry safety; the remaining gaps are real but not fatal.

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 description coverage is only 33%: body.action_type and playlist_item_ids have no schema descriptions, and only device_id and profile do. The description explains the meaning of the two action_type values, partially compensating, but gives no guidance on playlist_item_ids format, batch size limits, or behavior for invalid/missing ids.

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 opens with a specific verb+resource+scope: 'Show or hide several playlist items on a device at once', which tells an agent this is a batch visibility toggle, distinct from the single-item update_playlist_item sibling. It also pins the endpoint (POST /api/devices/{device_id}/playlist_items/bulk), removing ambiguity.

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?

It names the valid action_type values (hide/show) and explicitly routes deletion to deletePlaylistItem, which is a real alternative-selection cue. It doesn't contrast with trmnl_update_playlist_item for single-item edits, so the sibling boundary is only partly drawn.

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