Delete a block from Wave Terminal by block ID; first call returns confirmation, then pass approved=true to execute. Requires the Seashell Helper block.
Delete a block from Wave Terminal. First call returns a confirmation; pass approved=true to execute. Requires the Seashell Helper block.
| Name | Required | Description | Default |
|---|---|---|---|
| approved | No | Set to true to confirm and execute | |
| block_id | Yes | Block ID to delete |
Changes observed during successful MCP inspections.
v2.2.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses the confirmation flow and helper-block prerequisite, but it does not state whether deletion is irreversible, what permissions are required, or what happens to existing block 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?
Three short sentences, front-loaded with the core action, followed by the confirmation flow and prerequisite. Every sentence contributes directly to correct invocation.
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?
Given two parameters, no output schema, and no annotations, the description covers the essential execution flow and prerequisite. It is nearly complete for invocation, though it leaves out post-deletion behavior and failure modes.
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 the schema already defines block_id and approved. The description adds the first-call confirmation behavior around approved, but does not add substantial meaning beyond the schema for either parameter.
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 and resource: deleting a block in Wave Terminal. It is distinguishable from widget-related siblings, but it does not explicitly contrast with wave_delete_widget or other deletion tools.
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 clearly explains the two-step invocation flow (first call returns confirmation, then approved=true) and names the prerequisite Seashell Helper block. It does not describe when to avoid this tool or when to use an alternative deletion tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.