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

Annotations already provide idempotentHint=true, readOnlyHint=false, and destructiveHint=false, covering basic behavioral traits. The description adds the requirement that the caller must be a host, which is useful context. However, it does not disclose side effects, such as whether the previous role is overwritten or if there are any cascading impacts. With annotations present, the description adds modest value.

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 consists of two sentences. The first clearly states the purpose and scope, including the range of allowed roles. The second efficiently provides requirements and constraints. Every sentence adds value, with no redundancy or fluff.

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?

Given the tool has 4 parameters (including one nested object), no output schema, and annotations present, the description covers the basic purpose, required inputs, and caller authority. However, it lacks details on error conditions, what happens if the staff member does not exist, or the exact response. For a mutation tool, this is adequate but not thorough; additional information about expected outcomes or failure modes would improve completeness.

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 description coverage is 0%, so the description must compensate. It mentions 'event_id + user_id and a role and/or permissions', listing three of four parameters but omitting any semantics for the 'permissions' object (e.g., what keys are expected, how values work). The 'role' parameter's enum values are listed, but the description does not clarify that role and permissions are individually optional (schema does not require either). This leaves ambiguity about how to correctly use the permissions object.

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 clearly states the tool's purpose: 'Change an existing staff member's role and/or permissions on a live event.' It includes a specific verb ('change'), resource ('staff member's role and/or permissions'), and scope ('on a live event'). The list of possible roles in parentheses adds detail. This distinguishes it from sibling tools like assign_role or promote_guest_to_staff.

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?

The description provides clear prerequisites: 'Requires event_id + user_id and a role and/or permissions; you must be a host.' It tells who can use the tool and what inputs are needed. However, it does not explicitly state when to use this tool over alternatives, such as when to choose this over assign_role or promote_guest_to_staff, nor does it mention situations when not to use it.

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