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

Annotations declare destructiveHint=true and readOnlyHint=false, so the description need not restate safety. But with eleven actions bundled under one entry point, the description never says which actions mutate or destroy state, which require elevated permissions, or that delete/moderate operations are irreversible — context the annotations cannot express per-action.

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?

It is a single front-loaded sentence with no filler, so there is no verbosity problem. The issue is under-specification rather than waste: one sentence is simply not enough surface area for an eleven-action dispatcher.

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 an eleven-action tool with a nested free-form params object, no output schema, and destructive semantics, the description is drastically incomplete. An agent cannot determine required parameters, return shapes, or per-action behavior from it.

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 0% and "params" is an untyped nested object, so the description carries the full burden of explaining per-action parameters. It offers only vague nouns (memberships, updates, deletion, moderation) and no mapping of which keys each action requires or accepts.

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?

"Manage ... groups" names a resource and lists the kinds of operations (memberships, updates, deletion, moderation), but the verb "manage" is generic and the enumeration only loosely mirrors the eleven enum actions. Nothing distinguishes it from siblings like socnet_page or socnet_post, so an agent must open the schema to understand scope.

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?

There is no when-to-use guidance, no prerequisites (e.g. admin role for moderation), and no mention of alternatives among the socnet_* siblings. The agent is left to infer that this tool owns all group-related work.

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