delete_tag

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

With no annotations supplied, the description carries the full disclosure burden. It usefully states the required `tags:manage` permission scope, but gives no indication of irreversibility, whether the tag is removed from all tagged entities, or what the response looks like for a destructive operation.

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?

Very short and front-loaded with the action name, then permission, then endpoint. The trailing 'Tags: Tags' line is a generated artifact that carries no information for an agent, but otherwise nothing is wasted.

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 single-parameter delete with no output schema and no annotations, the definition covers identity and authorization but omits the consequences of deletion (irreversibility, effect on already-tagged conversations) and any mention of error behavior for a missing id.

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?

Only one parameter and schema description coverage is 100%, with the schema itself marking `id` as a path parameter. The description's endpoint template reinforces that the id goes in the URL path, which is a small addition, so the baseline of 3 applies.

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 title-cased phrase 'Delete Tag' names a verb and resource, and the raw endpoint 'DELETE /api/v1/tags/{id}' confirms it operates on a single tag by id. However, it essentially restates the tool name and adds nothing to distinguish it from update_tag or delete_* siblings in the catalog.

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?

There is no when-to-use guidance, no mention that this is irreversible, no guidance on confirming before deletion, and no pointer to alternative approaches (e.g., removing a tag from a conversation instead of deleting it globally). The only conditional information is the required permission scope, which is about authorization rather than tool selection.

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