Delete Workspace Node

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

Description adds significant value beyond annotations: 'Permanently delete', 'check for downstream dependencies first', and 'resolves the node via get_workspace_node and blocks the delete if the ID does not exist'. No contradiction with destructiveHint: true.

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 sentences plus a brief Args list—every sentence earns its place. Purpose is front-loaded, no redundancy, and the structure is clear and efficient.

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?

Covers all aspects: purpose, caution about dependencies, pre-validation, optional confirmation parameter, and return value ('Confirmation message plus the resolved node name'). Adequate for an agent to decide and invoke.

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 100%, so baseline is 3. The description's Args section adds behavioral context (e.g., confirmed is optional and for user confirmation) and explains pre-validation logic, which goes beyond the schema's parameter descriptions.

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 clearly states 'Permanently delete a workspace node', specifying the action (delete), resource (workspace node), and permanence. It distinguishes from sibling tools like update_workspace_node or create_workspace_node.

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?

The description explicitly warns 'Destructive — check for downstream dependencies first', providing guidance on when to use caution. It also mentions pre-validation (block if ID not found). While it doesn't name specific alternatives, it implies usage context for deletion.

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