Delete Group

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states that member models are not affected, deletion applies only to the grouping wrapper, and systems cannot be deleted through this API. This is meaningful context beyond the tool name.

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 compact and front-loaded with the core action. There is slight redundancy in stating twice that member models are unaffected, but overall it is well-structured and avoids unnecessary 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?

The description covers the essential operational context for a delete tool: what gets deleted, what does not get deleted, and an explicit unsupported use case. An output schema exists, so return value details are not required. The main omission is the purpose of server_version.

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 coverage is only 50% because server_version has no description. The description adds useful meaning to tag_id by explaining tags are 'overlapping, semantics-free grouping,' but it never explains what server_version is or how it should be supplied. The description does not fully compensate for the missing schema detail.

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 and resource: 'Delete a tag group' with a clear scoping statement that only the grouping is removed, not member models. It also distinguishes itself from other delete_* siblings by emphasizing that deletion is supported for TAGS ONLY.

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 an explicit when-not-to-use signal: 'Deletion is supported for TAGS ONLY — systems have no delete endpoint on this API.' This prevents misuse on systems, though it does not name a specific alternative tool for system deletion.

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