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

Annotations only supply destructiveHint=false, so this description carries most of the behavioral load and does so well: it discloses the two-phase preview→confirm write protocol, the required hash plus consent flag, the server-side permission re-verification, and the update semantics where an omitted field means unchanged and null means cleared. It does not describe what list returns or what happens on a stale/expired previewHash, but the safety-critical paths are covered.

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 very short and front-loads the auth requirement and the op list, and every clause carries information. However it is a single semicolon-chained run-on with no separation between op semantics, parameter rules, and the preview/confirm protocol, which makes it easy to mis-parse despite the low word count.

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 11-parameter, nine-operation tool with zero schema coverage and no output schema, the description covers the op space, the parameter rules, and the destructive-safety workflow, which is the bulk of what an agent needs. Remaining gaps are modest: return shape of list, the meaning of id, and failure modes for confirm are not stated.

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 the nested fields object is untyped (additionalProperties: {}), so the description must compensate and largely does: it explains fields as shared group/venue fields, spells out null-vs-omit on update, ties userId+role(ADMIN/INVITER/null) to group set_role versus add for venues, and maps featured to the feature op. Only id and kind are left to inference, which keeps this just below a 5.

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 names the resource ("本人资源" / 共享群 / 场地) and enumerates the concrete lifecycle verbs it performs (list, create, update, pause, unlist, relist, confirm, set_role, feature), so an agent knows this is a self-scoped CRUD/state tool for groups and venues. It stops short of naming a sibling tool it is not, so differentiation from neighbours like draft_community_resource or community_resource_requests relies on the title rather than the text.

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?

Usage is effectively given per operation: read with list, mutate public info with create/update, change visibility with pause/unlist/relist, and it explicitly states that writes default to preview and that confirm must be called with previewHash/consent=true/preview=false. The leading "登录" establishes the auth prerequisite and "服务重验本人权限" states the server-side permission check. What is missing is any when-not guidance or pointer to the competing sibling tools in this large catalogue.

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