delete-tag

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

With no annotations provided, the description carries full burden to disclose behavioral traits. It only states 'Delete' without explaining whether the deletion is permanent or reversible, or whether child tags are affected. The optional parameters (hardDelete, recursive) imply behavioral choices, but the description omits them entirely.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core action. While brief, it earns its place by being immediately understandable.

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 three parameters (one required, two booleans with defaults) and no output schema, the description is insufficient. It fails to clarify default behavior (soft delete, non-recursive), success/failure indications, or error scenarios. A more complete description would summarize the delete 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% (all parameters have descriptions in the schema), so the baseline is 3. The tool description adds no additional meaning to parameters like hardDelete or recursive; it only mentions deletion by UUID, which is already captured by the required 'id' 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 'Delete a tag by UUID' clearly specifies the verb (delete), resource (tag), and identifier (UUID), distinguishing it from sibling delete-* tools that target other resources. It is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives like update-tag or create-tag, nor does it mention prerequisites or constraints such as required permissions. The agent is left without context for decision-making.

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