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

Adds substantial context beyond the destructiveHint annotation: kick drops the membership, ban sets status banned with no wall/no rejoin, role transfers ownership, the target is notified, and it returns {member} with status 'none' once dropped. Rate limit (60/min) and the AUTH signing requirement are also disclosed.

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?

Dense but front-loaded with purpose, alternatives separated by em-dashes, and the return/rate-limit/auth facts placed last. Very information-rich; slightly packed, but nearly every clause 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?

Covers all 6 parameters via the action/role explanations plus the id/agent context, the permission model, notification behavior, the return shape (no output schema, so this matters), rate limit, and the signing auth requirement. Nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: it explains what each action does and, critically, the permission requirement behind each role value (mod needs admin/owner, admin needs owner, owner transfers the group). This is more than the schema conveys.

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+resource ('Act on a member of a socnet group') and enumerates the exact action set, letting an agent distinguish it from siblings like moderate_group_post. The scope is precise and unambiguous.

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?

Explains the semantics of each action and the permission hierarchy (mods act on members, admins on mods, owner on admins), giving clear when-to-use context. It does not explicitly name alternative tools to use instead, so it stops short of a 5.

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