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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutating, potentially-impactful nature is covered. The description adds the role-effect semantics (EDITOR can change things, VIEWER read only) and the ownership prerequisite, but says nothing about reversibility, notification of the affected member, or self-demotion restrictions.

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?

One tight sentence that front-loads the action, then the scope, then the role glossary. No wasted words.

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 3-required-param mutation with no output schema, the definition covers the action, allowed values, and ownership precondition. It omits the effect on the target user, permission edge cases, and return behavior, leaving moderate gaps.

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 three parameters rely on the description for meaning. It explains what EDITOR and VIEWER mean, which is real value beyond the bare enum, but boardId and userId semantics are left entirely to their names.

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?

States a specific verb and resource ('Changes a member's role'), plus the scope ('on a board the user owns') and enumerates the two target roles. An agent can distinguish this from remove_member or share_board, though siblings are never named.

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?

Implies the precondition that the caller must own the board, which is useful context for when invocation is valid. However, there is no explicit when-to-use-vs-alternative guidance (e.g., use remove_member to revoke membership entirely, or share_board to grant access).

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