Remove specific tag key-value pairs from an entity while preserving the key if other values remain.
Delete specific tag key-value pairs from an entity (keeps the key if other values remain).
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | Entity GUID | |
| account_id | No | Account ID (optional) | |
| tag_values | Yes | Tag key-value pairs to delete as [{key, value}] |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the burden. It does disclose what is destroyed (the listed key-value pairs) and a key behavioral nuance (the key remains if other values remain). However, it does not mention account_id scoping, permissions, partial failure behavior, or response details, so it is adequate but not rich.
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. The parenthetical packs crucial semantic nuance compactly, and every clause 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?
For a simple three-parameter tool, the core call semantics are covered and the schema fills in parameter details. However, the lack of guidance about sibling alternatives and the absence of any annotation or response information leave gaps an agent must infer. It is adequate but not fully complete.
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 baseline of 3 applies. The description adds no extra syntax, format, or edge-case detail beyond what the schema already provides for guid, account_id, and tag_values.
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 starts with a precise verb and resource ('Delete specific tag key-value pairs from an entity') and the parenthetical clarifies the key-retention behavior, distinguishing it from deleting an entire tag key. This is specific and unambiguous, especially alongside siblings like delete_tags_from_entity.
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 parenthetical implies this tool is for selectively removing values while preserving the key, but it never explicitly tells the agent when to prefer this over delete_tags_from_entity, replace_tags_on_entity, or add_tags_to_entity. No alternatives or exclusions are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.