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

Annotations already indicate destructive behavior (destructiveHint=true). The description adds value by disclosing that pending members can be removed, the owner-only restriction, and the ability to identify members by ID or email. These behavioral traits go beyond the annotations without contradicting them.

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, front-loaded sentence conveys the action, scope, and permission requirement. No filler or redundant phrasing. Every word adds value.

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 simple tool with fully described parameters and annotations indicating destructiveness, the description is reasonably complete. It covers purpose, target scope, identification method, and permission. The lack of an output schema and the absence of edge-case details (e.g., no matching member) are acceptable given the schema's completeness.

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 the baseline is 3. The description simply restates the two identifier options ('member ID or email') without adding new meaning beyond the schema's descriptions. It does not, for example, clarify the 'first matching member' behavior for email, which is present in the schema.

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 clearly states the action ('Remove'), the resource ('member'), the project context ('from this project'), and the identification methods ('member ID or email'). It also specifies member statuses ('accepted or pending'), distinguishing it from sibling tools like set_member_role or invite_member.

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?

The description implies usage when a member needs to be removed and adds an 'Owner only' permission constraint, but it does not explicitly state when not to use the tool or mention alternatives (e.g., use set_member_role to change a role instead). Thus, usage context is clear but alternative guidance is absent.

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