Delete multiple look board buttons at once by providing button IDs and confirming deletion, streamlining cleanup of unwanted lighting controls.
Delete multiple buttons in a single operation.
| Name | Required | Description | Default |
|---|---|---|---|
| buttonIds | Yes | Array of button IDs to delete | |
| confirmDelete | Yes | Confirm deletion (required to be true for safety) |
Changes observed during successful MCP inspections.
v1.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not state that deletion is irreversible, what happens to buttons still referenced by a look board, or what the response contains. The safety confirmation flag is only visible in the schema, not explained here.
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?
A single front-loaded sentence with no filler. It is efficient, though possibly too terse given the destructive nature of the operation.
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 two-parameter destructive mutation with no annotations and no output schema, the description is thin. The schema covers the confirmation requirement, but irreversibility and side effects on referencing look boards are never addressed.
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 100%, so both parameters (buttonIds, confirmDelete) are already documented inline, including the safety rationale for confirmDelete. The description adds no additional meaning beyond the schema, which is the expected baseline for full 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?
The description states a specific verb ('Delete') and resource ('buttons'), with the bulk scope made explicit by 'multiple ... in a single operation'. It is clear enough to distinguish from single-button deletion and from the sibling bulk_delete_look_boards, though it does not name any sibling.
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 guidance on when to use this versus deleting buttons individually, updating them via bulk_update_look_board_buttons, or other bulk operations. No prerequisites or conditions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.