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

Beyond the minimal destructiveHint=false annotation, the description discloses important behavior: login/organizer requirement, SPEAKER-only scope, no reordering, vector+model cost and ten-plus-second latency, a pause for human review, and an exit path when no new people are found. It still does not clarify exactly what is persisted or how candidates are returned, so it is strong but not exhaustive.

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 dense and front-loads the access and role constraints, then the workflow, then cost and post-completion behavior. It uses compact arrow notation and jargon such as 'exits' that may slow comprehension, but nearly every phrase carries operational meaning.

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 complex, model-backed candidate generation tool with no output schema, the description covers access, role limits, cost/latency, workflow sequencing, review pause, and the no-new-candidates case. It is still somewhat terse about what the tool returns and what 'exits' concretely means, leaving minor gaps for an agent.

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%, so the schema already documents both parameters, including the role enum and the server-side rejection of ATTENDEE. The description repeats the SPEAKER-only constraint but adds no new syntax or format details for activityRef or role beyond what the schema provides, which matches the baseline of 3.

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: append guest candidates for SPEAKER only and explicitly says it does not reorder. This distinguishes it from reordering or automatic ATTENDEE matching, but the core effect of generating a new candidate batch is only implied through the title and the workflow reference to set_guest_invite_plan.

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 an explicit workflow: set_guest_invite_plan changes the brief, then this tool runs, then get_activity_invites is used for review. It also states hard restrictions (SPEAKER only; ATTENDEE cannot be supplemented), warns against calling twice in one conversation, and says to pause and confirm before calling set_guest_invite_plan_status(start).

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