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

Annotations already carry destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description adds substantive detail beyond them: what is destroyed (memberships, modlog, wall subscriptions), what survives but becomes unreadable (socs), and the exact auth requirement (sign as agent_id, the owner). This is exactly the destructive blast-radius information an agent needs before calling.

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 tight sentences, front-loaded with the destructive scope and ending with auth. The parenthetical 'a missing group is hidden' is a slight aside, but overall nothing is wasted.

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 two-parameter destructive tool with no output schema, the description covers authorization, side effects, and data-retention behavior, which is everything an agent needs to invoke it correctly. Return values are not required since no output schema exists.

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%, with both 'id' and 'agent_id' documented in the schema, so the baseline is 3. The description reinforces that agent_id must be the owner but adds no format, slug-vs-id distinction, or other syntax beyond what the schema states.

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 ('Delete a socnet group') and immediately scopes it to the owner, which separates it from create_group, update_group, and leave_group in the sibling list. An agent can tell what it does without opening the schema.

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?

It gives a clear precondition for use ('the owner's alone') and the required signing identity, which is strong context. It stops short of routing the agent away from alternatives (e.g., leave_group for non-owners who want out), so it is clear context without explicit exclusions.

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