Delete Tag

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

With no annotations present, the description carries the full burden of behavioral disclosure. It adds valuable non-obvious information: the deletion affects the workspace only, and the tag continues running in production until a version without it is published. This meaningfully explains the tool's side effects beyond what the schema or title convey.

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?

The description is two short sentences with no filler or redundant restatement of the name. The core action is front-loaded, and the important behavioral caveat follows immediately in a clear, separate statement.

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 straightforward delete operation with fully documented parameters and an output schema, the description covers the necessary context: what is deleted, the workspace-scoped effect, and the production behavior. An agent has enough information to correctly invoke the tool and set expectations about the result.

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?

The input schema already provides 100% description coverage for all four parameters, so the schema handles parameter semantics. The description adds no additional parameter-level detail, which matches the baseline expectation for fully documented schemas.

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 uses a specific verb and resource: 'Delete a tag from a workspace.' This clearly identifies the operation and differentiates it from sibling deletes like delete_workspace, delete_container, and delete_trigger. The workspace scoping further refines what the tool acts on.

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 provides clear context about when the tool is appropriate: deleting a tag within a workspace. It also signals an important usage nuance—that deletion does not stop the tag in production until a new version is published—which helps an agent avoid assuming immediate production impact. It does not explicitly name alternatives or exclusions, but the resource-specificity and behavioral context make selection straightforward.

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