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

The description goes well beyond the annotations by disclosing important behavioral constraints: admins cannot act on owners, the last owner cannot be demoted, and an ownerless account cannot be administered. These are exactly the kind of edge-case and authorization traits an agent needs before calling a mutating tool.

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 compact and front-loaded: the core action comes first, followed immediately by the critical constraints. Every sentence earns its place, with no filler or repetition of schema content.

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 two-parameter role-change tool with full schema coverage, an output schema, and annotations indicating mutation without destruction, the description provides all necessary context. The ownership and admin restrictions are the key contextual details an agent needs, and they are present.

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 100%, and both parameters already have clear, detailed descriptions in the schema. The tool description itself adds little parameter-level meaning beyond the word 'promote or demote', so the baseline of 3 is appropriate.

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 action with 'Promote or demote someone', which combined with the title makes the tool's purpose unambiguous. However, it does not explicitly compare against sibling tools like invite_member or remove_member, so it stops short of full sibling differentiation.

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 intended usage is implied: use this when you need to change a member's role. It does not explicitly state when to prefer this over invite_member or remove_member, nor does it state when not to use it, aside from the ownership constraints. The 'Call list_members if unsure' guidance is helpful but appears only in the parameter schema.

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