set_participant_role

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

With annotations covering safety (readOnly=false, idempotent=true, destructive=false), the description still adds substantial operational context: permission requirements, the owner-vs-moderator power asymmetry, the irreversibility of removing an owner, and Talk 25 availability constraints. Nothing contradicts the annotations.

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-loads the action and then the permission semantics; the owner paragraph is dense but each rule is actionable. Slightly verbose relative to a three-parameter setter, but nothing reads as filler.

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?

An output schema exists, so return values need only a one-line pointer ('JSON with the participant afterwards'), which is present. Combined with the permission rules and role semantics, an agent has everything needed to call this 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 0% and the schema carries no descriptions or enums, yet the description documents all three parameters, including the allowed role values and the provenance of attendee_id ('from get_participants'). It fully compensates for the schema gap.

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 ('Make a participant owner, moderator or plain user') and enumerates the exact role values being set. It is clearly distinguishable from siblings like add_participant, remove_participant, and get_participants.

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 rich when-it-works conditions: requires moderator rights, owner rights to create/demote owners, guest/group/team restrictions, and the last-moderator rule. It does not explicitly name an alternative tool or a 'use X instead' path, so it stops short of a 5.

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