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

Strong disclosure beyond the annotations: login requirement, the write-defaults-to-preview flow, the exact confirmation recipe (same params + previewHash + consent=true + preview=false), and the caveats that acceptance does not imply WeChat-group membership and venue confirmation does not imply payment. These are non-obvious behaviors an agent cannot infer from readOnlyHint=false and openWorldHint=true alone.

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, opening with the login requirement and organizing subsequent clauses by action with semicolons. Nearly every clause carries information, though the run-on density makes it slightly harder to parse than an ideally structured description.

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 14-parameter multi-action tool with no output schema and only weak annotation coverage, the description supplies the key procedural knowledge: action routing, cursor strategy, and the preview/confirm safety protocol with its caveats. A few parameters (limit, note, status enum semantics) remain undocumented, keeping it just short of fully complete.

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?

With 0% schema description coverage, the description must carry the load and largely does: it ties kind/box/status to pagination, groupCursor/venueCursor to mixed-list paging, requestId to get, and previewHash/consent/preview to the confirm step. It leaves limit, note, cursor, and the status enum values unexplained, so compensation is substantial but incomplete.

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 enumerates the three operations (list/get/respond) and the resource they act on (group/venue requests), so an agent knows this is a request-management tool. It does not, however, distinguish itself from any sibling such as manage_my_community_resource or contact_community_resource, so differentiation is left implicit.

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 per-action routing (list paginates by kind/box/status, mixed lists split across groupCursor/venueCursor, get reads requestId, respond uses accept/confirm/decline/cancel) and a genuine when-condition for organizer_confirm (only after offline negotiation). No alternative sibling tools are named, so it stops short of explicit when-to-use-this-vs-that guidance.

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