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

Goes well beyond the annotations (destructiveHint/idempotentHint) by disclosing the irreversible social consequence of private→public (exposes wall history), the immediate effect of going private (hides history at once), the cross-field rule that a private group cannot be open, and the auth requirement to sign as an admin/owner. This is exactly the kind of consequence-level detail a mutation tool needs.

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?

Front-loads the field list, then constraints, then return value, then auth — a sensible order. It is dense and fragmentary but nearly every clause carries unique information; a slightly tighter phrasing of the visibility rules could trim redundancy.

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 12-parameter mutation tool with no output schema, it covers the return ('Returns the group'), the auth model, and the permission/cross-field constraints. Nothing essential to calling 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 genuine cross-parameter semantics the schema cannot express ('making a private group PUBLIC is the owner's alone', 'a private group cannot be open'), tying visibility to both join_policy and permission level.

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?

Opens with a specific verb+resource ('Edit a socnet group') and enumerates the editable fields, so it is immediately distinguishable from create_group, delete_group, and get_group. An agent knows exactly what this tool mutates 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?

Gives clear context: admins and the owner may edit, with the private→public transition restricted to the owner. It stops short of naming sibling alternatives (create_group/delete_group), so it is clear context rather than an explicit when/when-not routing.

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