Delete a custom posture attribute from a device in your Tailscale tailnet. Use this action to remove outdated or incorrect custom attribute data permanently.
Delete a custom posture attribute from a device. This is irreversible.
| Name | Required | Description | Default |
|---|---|---|---|
| deviceId | Yes | The device ID | |
| attributeKey | Yes | The attribute key to delete (e.g. 'custom:lastAuditDate') |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, but the description adds the crucial behavioral trait 'irreversible,' which informs the agent that the operation cannot be undone. This adds value beyond the annotations.
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?
Two concise sentences with no fluff. The first sentence front-loads the action and resource. Every word earns its place.
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 the tool's simplicity (2 required params, no output schema), the description covers the essential aspects: purpose and irreversibility. Could mention response details, but not critical for a delete operation.
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% with clear parameter descriptions. The description adds an example for attributeKey ('custom:lastAuditDate'), which enhances understanding without repeating schema info.
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 the action (Delete) and the resource (custom posture attribute from a device). It is unambiguous and distinguishes itself from sibling tools like tailscale_set_device_posture_attribute.
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 lacks explicit guidance on when to use this tool vs alternatives (e.g., batch update or set). It only provides a basic indication of irreversibility, which is not enough for optimal agent decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.