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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the description correctly does not contradict it. The description adds the behavioral constraint that the target must already be a workspace user. It does not disclose whether an invitation email is sent, what happens if the user is already a member, or whether the action is idempotent.

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 compact sentence with no filler, and the key scoping constraint ("existing workspace user") lands early. It is efficient, though the title restates the same intent, so the sentence does not carry much extra payload.

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 three-required-parameter mutation tool with no output schema, the description is thin: it omits whether an invite/notification is sent, behavior on duplicate membership, and how this differs from members_set_role. An agent has enough to attempt the call but not enough to predict its consequences.

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 carries the full burden, and it only loosely gestures at the three parameters (company = companyId, user = email, "given role" = role). It adds no format, constraint, or semantics for email/companyId and never explains the role enum values, so the schema is not meaningfully supplemented.

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 action and resource: granting an existing workspace user access to a company at a given role. The phrase "existing workspace user" usefully distinguishes it from creating a user. However, it never differentiates itself from close siblings like members_set_role or members_remove, which an agent must disambiguate on its own.

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 a precondition ("existing workspace user"), which tells the agent this is not a user-creation path, but it gives no explicit when-to-use guidance and never names the alternative members_set_role, which appears to overlap heavily. Usage is inferable rather than stated.

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