Delete Space 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 that the action 'changes community state' and gates it behind confirm=true, which is real extra context, but it is vague about what state changes and silent on irreversibility or cascade effects on group members.

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 no filler, and the confirm precondition is front-loaded alongside the destructive action. Slightly terse for a destructive operation, but structurally clean and appropriately sized.

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 with no output schema, the description covers the action and the confirm gate but omits what a delete actually destroys (member assignments, associated spaces) and whether it is reversible. Adequate, but the agent must guess at blast radius.

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 account, confirm, and space_group_id are all documented in the schema itself (including the confirm semantics). The description only echoes the confirm requirement, adding no syntax or format meaning beyond the schema. Baseline 3 applies.

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 verb and resource ('Delete Space Group'), but that is a literal restatement of the tool name and title, adding no distinguishing detail. With siblings like delete_space, delete_space_group_member, and archive_access_group in the list, the agent gets no help telling them apart. Minimum-viable rather than clear-and-differentiated.

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 sentence 'requires confirm=true for the user-requested action' implies a usage precondition (only when the user explicitly asked), which is useful. However, it names no alternatives and gives no when-not guidance relative to delete_space, delete_space_group_member, or member-removal tools, so the routing decision is left to inference.

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