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

Annotations only declare readOnlyHint=true, and the description adds real context beyond that: a login/organizer authorization requirement, the fact that draft (unconfirmed) guests appear in the result, and the meaning of confirmed=true (visibility on the public page and poster). It does not mention ordering, result volume, or pagination for what could be a long guest list, so it stops short of a 5.

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?

Front-loaded with the access qualifier and the core action, then flows into sibling routing and field semantics using compact arrow notation. Dense but every clause carries information; the arrow shorthand ('guestId → create_guest_invite_link') is terse at some cost to readability.

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 read-only, single-parameter listing tool with no output schema, the description supplies the key field semantics an agent needs to act (guestId, confirmed, userId) plus the auth requirement. It leaves the overall result shape and any size limits unstated, which is a modest gap rather than a blocking one.

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 activityRef is already documented as a slug or id from list_my_activities. The description adds nothing further about this parameter, so the baseline 3 applies; the value it adds lives in return-field semantics rather than input semantics.

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 and resource ('列一场活动的嘉宾阵容') plus the crucial scope detail that unconfirmed draft rows are included. The bracketed '[需要登录·主办方]' qualifier further distinguishes it from public-facing sibling listings such as list_activity_cloud_contact_requests or get_activity_guest_collection.

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?

Explicitly routes the agent: use this to obtain guestId, then call create_guest_invite_link to mint a self-service card; people absent from the lineup must first go through add_activity_guest. Both the follow-on action and the prerequisite action are named, which is exactly the when/when-not guidance the dimension asks for.

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