Delete Tag

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the specific permission scope required, the delegation-token caveat, and the note that the action may share access, notify people or incur provider charges.

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?

Purpose is front-loaded in a single clean line, but the body is dominated by a long permission block and a full paragraph on delegated-token authorization, plus a generic boilerplate sentence about side effects. The core action is buried under compliance text.

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 destructive delete with no output schema and fully documented parameters, the description covers the key operational needs: authorization requirements, the confirm gate, and potential side effects. It is close to complete, with only the lack of an explicit alternative-selection cue as a gap.

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%, so 'name', 'account' and 'confirm' are all documented in the schema itself. The description only echoes the confirm=true requirement, adding no syntax, format, or edge-case detail beyond what the schema already provides; baseline 3 is appropriate.

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 ('Deletes') and resource ('a tag'), which cleanly distinguishes it from the read/list siblings (list_tags) and creation siblings (create_tags, bulk_tag). It does not explicitly name an alternative, but the destructive verb leaves no ambiguity about what the tool does.

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 supplies prerequisites (required token permission, delegation-token behavior, mandatory confirm=true) which give useful invocation context. However, it never states when to reach for this tool versus the other tag operations, nor any conditions under which it should be avoided, so usage guidance is implied rather than explicit.

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