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

With no annotations, the description carries the full burden and delivers real behavioral context: changes propagate on the member's next request including their API keys, the owner's role is immutable, and admin grant/revoke is owner-only. It doesn't cover reversibility or failure/error behavior, hence not a 5.

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?

Three dense sentences, front-loaded with the action and its main modifier, then propagation semantics, then authorization constraints. No filler and every sentence adds 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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers purpose, scoping, timing, and authorization limits well. The remaining gap is identifier meaning for workspaceId/accountId and what a caller observes on failure.

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 does well for agentIds ('limit a viewer/editor/operator to selected agents', 'null = all agents') and clarifies role tiers, but workspaceId and accountId are left entirely unexplained by both schema and description.

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 names a specific verb (change role) and resource (member) and adds the agentIds scoping facet, which nothing else in the schema explains. It does not explicitly contrast itself with siblings like members_transfer, members_remove, or members_revoke, but the intent is unambiguous.

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 states the caller precondition (Admins) and hard exclusion rules ('The owner's role cannot change; only the owner grants or removes admin'), which tell the agent when this call will and won't succeed. It stops short of naming alternative tools for adjacent tasks.

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