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 real value on top: the specific permission scope required, the confirm=true gate for the mutation, and the side-effect warning 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?

The core statement 'Deletes a tag' is front-loaded and clear, but the permission block is verbose boilerplate that consumes most of the text. It is organized with headers, though it could be trimmed without losing meaning.

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, non-idempotent tool, the description supplies the auth requirements and the confirm gate, complementing the safety annotations. With no output schema, nothing about return values is needed; the definition is close to complete for correct invocation.

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 fully documented in the schema. The description only restates the confirm requirement already captured by the confirm property, adding no syntax or format detail beyond the schema baseline.

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 ('Deletes a tag'), which is unambiguous on its own. It does not, however, differentiate itself from tag-related siblings such as bulk_tag, create_tags, or list_tags, so an agent gets no routing help from the description.

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 never says when to use this versus bulk_tag or another deletion path, and offers no prerequisites beyond an auth/confirm requirement that is operational rather than usage-routing. There is no explicit when/when-not guidance.

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