rm_delete_tag

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

Annotations already mark this as destructive, and the description reinforces that with 'Destructive' while adding the critical behavioral requirement that confirm=True is necessary. This goes beyond the schema default and tells the agent that simply calling the tool without confirm will not perform the deletion.

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 one short sentence that front-loads the core action and immediately warns about the destructive guard. Every word earns its place; there is no fluff or redundant detail.

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 delete operation with an output schema and destructive annotation, the description covers the essential safety behavior and the confirm requirement. It does not mention side effects like cascading deletions or whether deletion is reversible, but those are less critical given the tool's simplicity.

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 0%, so the description must compensate. It explains the confirm parameter's role clearly, but tag_id is left with only its name and type from the schema. The description adds partial value but does not fully document the semantics of the required 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 states the exact action and resource: 'Delete a tag'. It is specific and clearly distinguishes this tool from sibling tools like rm_create_tag and rm_list_tags by naming the delete operation on the tag resource.

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 implies when to use the tool: when a tag must be deleted. It also gives a key usage condition ('requires confirm=True'), but it does not explicitly discuss alternatives or when not to use it, such as preferring deactivation over deletion.

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