Delete a tag

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

Annotations already mark destructiveHint=true, so the description adds useful context beyond that: the two-phase confirmation-token requirement and the reassurance that pages themselves are not deleted. This is meaningful behavioral disclosure.

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?

Three short sentences, each earning its place: the primary effect, the non-destructive impact on pages, and the required confirmation token. No filler or redundancy.

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?

The description plus schema covers the full workflow: effect, scope, and confirmation-token protocol. It is complete enough for an agent to call the tool correctly, though it could be slightly clearer about what the first unconfirmed call returns.

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%, and both parameters are already well documented, including how confirm_token should be obtained. The description's mention of a confirmation token adds no new parameter-level meaning, so the baseline score 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?

States a specific verb and resource: 'Removes a tag from the wiki and from every page that carries it.' It also disambiguates scope by clarifying that pages themselves are untouched, distinguishing this from page-deletion and tag-update tools.

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 intended use is implied clearly by the description—use this to globally remove a tag—and it mentions the confirmation-token prerequisite. However, it does not explicitly contrast with alternatives such as update_tag or explain when not to use this tool.

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