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

The annotations already declare destructive=true, idempotent=true, and readOnly=false, so the mutation profile is covered. The description adds useful authorization behavior beyond the annotations, especially the owner-only rule for OWNER grants and removals.

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 two compact sentences with no wasted wording. The operation and the most important authorization constraint are front-loaded.

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 three-parameter mutation tool with destructive and idempotent annotations already present, the description covers the core purpose, role values, and authorization limits. It does not describe success behavior or edge cases such as self-role changes, but those gaps are relatively minor given the annotation and schema support.

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 67%; teamId and memberId are documented in the schema, while role has only an enum. The description adds meaning by naming the three role values and clarifying that OWNER changes require an owner, which is not conveyed by the enum alone.

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 operation on a member resource: setting the role to MEMBER, ADMIN, or OWNER. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as invite_member or remove_member.

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 meaningful caller constraints: owners and admins may use it, and only owners can grant or remove OWNER. This clarifies when the tool is permitted and when OWNER changes are restricted, but it does not name alternative tools or explain other conditions such as changing one's own role.

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