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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is known. The description adds nothing beyond that: it does not explain what happens to the previous role, whether owner promotion transfers ownership, whether the last owner can be demoted, or what errors occur on permission failure.

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?

A single four-word sentence is technically efficient and front-loaded, but for a destructive three-parameter mutation it is undersized rather than concise; the one sentence does not earn its place as a usable definition.

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, non-reversible-privilege mutation with 33% schema coverage and no output schema, the description should explain permission requirements and role semantics. Neither is present, leaving the agent dependent on the annotations and the partially documented schema.

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 only 33% – only orgId carries a description ('Organization ID from org_list'). The description mentions no parameters at all, so it does not compensate for the undocumented userId or clarify that 'role' accepts exactly owner/admin/member or what each role grants.

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 'Changes a member's role' is essentially a paraphrase of the tool name (org_member_set_role) and title ('Change member role'), which is the definition of tautology. It does identify a verb and resource, but adds no distinguishing information such as which org/user scope applies or how it differs from org_member_list or org_member_remove.

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?

There is no guidance on when to use this tool versus siblings like org_member_remove or org_invite_create, and no mention of prerequisites such as caller permissions (owner/admin required to change roles). The agent must infer everything from the name alone.

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