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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior the annotations cannot: an organizer-authentication requirement, a hard truncation threshold (>500 registrations) that also makes noShow incomplete, and the restriction that walkIn appears only for public events. These are exactly the operational caveats an agent needs before trusting the result set.

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: the access constraint leads, then scope, then caveats, then alternatives, with semicolons separating each concern. Every clause carries information, though the run-on structure is harder to scan than a short bulleted form.

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?

There is no output schema, so the description carries the burden of describing the payload - and it does: what is included (noShow/walkIn), what is excluded (ticketing/contact/answers), and the truncation caveat. An agent has everything needed to call and interpret this tool correctly.

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 the single activityRef parameter is already documented as accepting a slug or id from list_my_activities / get_organizer_activity. The description adds no further syntax or format detail, so the baseline 3 for schema-does-the-work is correct.

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?

States a specific verb+resource (get_activity_attendance = the union of registration ∪ check-in lists) and immediately bounds it: includes noShow/walkIn, excludes ticketing/contact info/answer sheets. This lets an agent separate it from siblings like get_activity_invitation_ledger or list_activity_guests without opening a 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 a clear access precondition (【需要登录·主办方】 - login required, organizer) and names two alternative routes: check_in_attendees for supplemental entry during the compatibility window, and start_activity_match_round for actual-attendance grouping. It never states when NOT to use this tool versus, e.g., the invitation ledger, so it falls short of a full when/when-not treatment.

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