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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the key context of 'soft-delete', indicating the tag is not permanently destroyed but hidden or marked as deleted, which is valuable beyond the annotations. It also notes the tag is 'shared across customers and reviews', giving insight into its scope. No contradiction with annotations.

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 exceptionally concise: two sentences, zero filler. The key action ('Delete Tag') is front-loaded, followed by a precise clarification of the deletion behavior and scope. Every word earns its place.

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 tool with an output schema present, the description covers the essential behavioral aspects: what is deleted, how (soft-delete), and its shared scope. It does not discuss side effects or return values, but the output schema handles return details, and the annotations cover destructive/idempotent behavior. The information is sufficient 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?

The schema description coverage is 100%, and the 'id' parameter is fully documented as a unique numeric identifier. The description adds no extra semantic detail about the parameter, so it neither enhances nor detracts from the schema. 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?

The description states a specific verb ('Delete') and resource ('Tag'), and clarifies it is a soft-delete of a workspace tag shared across customers and reviews. This clearly distinguishes it from createTag, updateTag, and listTags among the siblings. The purpose is unambiguous and precise.

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 provides clear context that this tool soft-deletes a tag, implying it is the appropriate choice for removing a tag from active use. It does not explicitly name alternatives or state when not to use it, but the scope is clear enough that an agent would not confuse it with create/update/list operations. There are no misleading cues.

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