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

Goes well beyond the destructive/idempotent hints by disclosing the actual effects ('Access ends immediately; task holds and browser views are reconciled') and the error semantics ('no row there is a no-op', unknown account is UNAVAILABLE). Admin-only authorization is spelled out, closing the main risk gap for a destructive mutation.

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 tightly packed sentences: capability first, argument forms second, effects and edge cases third. No filler, and the most decision-relevant facts (access ends immediately, admin-only) are not buried.

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?

With an output schema present and annotations covering the safety profile, the description only needed to add resolution rules, side effects, and authorization — and it covers all three. Nothing an agent needs to invoke this correctly 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 coverage is 100%, so the baseline is 3; the description nonetheless frames the conditional relationship between `member` and `workspaceId` and ties member resolution to outcomes (no-op vs UNAVAILABLE), which is meaning the schema does not convey. Some phrasing is near-verbatim with the schema, limiting the added value.

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 ('Remove a member or invite') and defines exactly what the `member` argument may be, so an agent can act without opening the schema. It does not, however, differentiate itself from the similar sibling `team_remove_member`, leaving the workspace-vs-team choice to be inferred.

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?

Gives clear operational preconditions: 'Workspace administrators only', row id usable alone, account id/alias/email requires workspaceId, and points at `workspace_member_list` as the id source. It stops short of explicitly excluding the team-level removal tool or stating when not to use this one.

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