Delete group

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds value beyond that with the authorization requirement ('Owner only') and a required confirmation step, both of which are behavioral facts the annotations don't convey. It stops short of saying what else is destroyed (members, group tracks), which is the one remaining gap.

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?

Two short sentences with zero waste; the permission constraint is front-loaded and the confirmation instruction follows immediately. Nothing to trim.

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 mutation with no output schema, the description covers permission and confirmation but omits the blast radius — whether group members, tracks, or content are removed with the group. An agent has enough to call it safely but not enough to advise the user on consequences.

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?

There is a single parameter (group_id) with 0% schema description coverage, and the description says nothing about it. The parameter name is self-explanatory in context, so the risk of misuse is low, but the description adds no semantic value over the bare schema.

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 group') plus a scope qualifier ('Owner only'), which distinguishes it from siblings like delete_set and delete_track. It's clear what the tool does, though it doesn't explicitly name the closest alternative for contrast.

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?

Gives a concrete pre-condition ('Owner only') and an explicit procedural instruction ('Ask the user for confirmation first'), which is genuinely actionable usage guidance. It doesn't mention alternatives, but deletion is unambiguous enough that this is not a major gap.

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