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

Goes well beyond the destructiveHint annotation by explaining exactly what is destroyed: setting role to owner demotes the acting owner to admin, transferring ownership irreversibly. It also discloses the authorization constraint and the self-modification restriction, which annotations cannot express.

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?

Four dense sentences, front-loaded with the action and the highest-risk consequence. No filler, no restatement of the title, and the warning appears before any parameter guidance.

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 destructive three-required-parameter mutation with no output schema, the description supplies the permission model, the self-restriction, the ownership-transfer consequence, and the prerequisite lookup. Nothing an agent needs to call it safely is missing.

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%, so all four parameters are already documented, including the enum note that owner transfers ownership. The description largely restates that and the user_id provenance already stated in the schema, adding little parameter-level meaning beyond what is structured.

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?

Starts with a specific verb and resource ("Changes a workspace member's role") and enumerates the exact target values (member, admin, owner). An agent can distinguish this from invite_workspace_member or remove_workspace_member without opening any schema.

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?

States the precondition clearly ("Only the workspace owner can do this, and not on themselves") and adds a confirmation requirement for the ownership-transfer case. It also routes the agent to list_workspace_members for the user_id, though it never names adjacent alternatives like remove_workspace_member or invite_workspace_member for role-adjacent operations.

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