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

The description significantly extends beyond annotations: it discloses the login/organizer requirement, batch limit, per-item independent execution with partial failure, idempotency details, side effects on published groups, exemption from the sign-in time window, and specific error codes. This is far richer than the readOnly/destructive/idempotent hints provided.

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?

The description is structured with labeled sections (前提, 何时用, 组合链, 口径) and a numbered list of constraints. Every sentence carries operational value, and the key trigger and limitations are front-loaded. The length is justified by the batch-check-in complexity.

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?

Given no output schema, the description covers all critical invocation context: authorization, input provenance, batch maximum, idempotency, side effects, error semantics, and a verification step via get_activity_attendance. The only minor omission is an explicit response shape, but the suggested follow-up workflow compensates for that.

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% and parameter descriptions already point to source endpoints. The prose adds meaningful semantics by explicitly rejecting phone numbers/nicknames in favor of internal userIds, explaining the rationale, and clarifying activityRef as slug or id from specific list endpoints. This goes beyond the generic schema description.

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 states a specific action ('批量核销' / batch check-in) on a specific resource (attendees of an activity), with a clear user-trigger scenario. It also clarifies the batch limit and contrasts it with the manual web interaction, making it distinguishable from sibling tools like bulk_review_signup_submissions.

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?

The description gives an explicit trigger ('用户报「这几位都到了，补一下」时') and a combination chain with specific sibling tools for obtaining userIds and verifying results. However, it does not explicitly name alternative tools it should be used instead of, so the vs-alternatives guidance is not fully complete.

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