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

readOnlyHint=true is consistent, and the description adds real behavioral facts beyond it: speakers contain guests only, audienceStats is counts without a roster because the audience is system-selected, and contacts are withheld except for a hasContacts flag. The organizer-role precondition is implied rather than stated, and nothing is said about size/volume of the payload.

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 front-loaded and wastes no sentences, but the telegraphic run-on style merges purpose, output caveats, link rules, and a three-step workflow into semicolon-joined fragments with dropped verbs, which costs parseability. Restructuring into short labeled clauses would keep the same content and read far better.

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?

With no output schema, the description carries the burden of describing returns and does so for the key fields (speakers, audienceStats, openInvite, hasContacts) plus the follow-up workflow. A read-only, one-parameter tool doesn't need much more, though the remaining response fields are still undocumented.

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 in the schema as a slug or id from list_my_activities / get_organizer_activity. The description adds no further meaning about the parameter, so the baseline 3 applies for a single fully-documented parameter.

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 (this activity's guest-invite overview) and enumerates what the payload covers: SPEAKER/ATTENDEE plans, status statistics, guest ranking/verdict/profile completion, and audience statistics. That is a specific read, not a restatement of the name. It stops short of naming the read siblings it overlaps with (get_activity_invitation_ledger, list_activity_guests, get_activity_guest_collection), and jargon like 判词/名次 makes the exact contents harder to pin down.

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 the caller an audience (organizer / logged-in) and two explicit 'don't do this' rules: openInvite already has a link so don't create another, and contact data isn't here so route through conversationId to start_conversation. It also sketches the escalation path (update_guest_candidates → set_guest_invite_plan_status(start) → send_guest_invite_now) with a 'confirm first' gate. No guidance on when to prefer it over the adjacent invitation/guest list reads.

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