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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description adds value by disclosing the owner-only privilege constraint and mandating confirmation before executing. It stops short of saying what happens to a removed member's data or whether removal is reversible beyond the idempotency hint.

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?

Extremely compact and front-loaded, with no filler sentences. The telegraphic phrasing 'action role (member_id from list_members, role)' is slightly ambiguous on first read but every token carries information.

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?

Annotations plus the output schema relieve the description of safety and return-value details, and the action-to-parameter mapping is present. Still missing for a destructive membership tool: which role values are assignable and their meaning, and what removing a member does to their existing records or owned resources.

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?

With 0% schema description coverage the description must carry the load, and it does map each action to the parameters it consumes and explains where member_id originates (list_members). It does not explain the semantics of the distinct roles (finance, security, viewer) or whether role/invitation_id are ignored on other actions, so a small gap remains.

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 enumerates the three concrete operations (change role, remove member, cancel invitation) and their respective parameters, so the agent knows exactly what the tool does. It is distinguishable from invite_member and list_members, though it never names those siblings directly.

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 tells the agent which action value pairs with which identifier (role/remove -> member_id, cancel_invitation -> invitation_id) and sources member_id from list_members. It also states a real precondition ('Owners alone add or remove owners') and a confirmation requirement ('Confirm first'), but offers no explicit routing to alternatives such as invite_member.

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