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

Annotations already declare destructiveHint, idempotentHint and readOnlyHint=false, so the safety profile is covered; the description adds real substance by explaining what the grant actually unlocks (opening the project, being assigned work, being @-mentioned) and clarifying that idempotency means role overwrite, not duplicate membership. It does not say what revocation looks like or whether the caller needs admin rights.

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 short sentences, front-loaded with the action and role list, then the reason it matters, then the idempotency caveat. No filler and no repetition of the schema.

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-parameter mutation with full annotations and no output schema, the description covers purpose, effect, defaults and idempotency. Gaps are minor: authorization requirements, behavior when the member belongs to another workspace, and role capabilities.

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% and the schema already documents the role enum, its EDITOR default, and that member accepts a UUID or email, so the description mostly restates what is structured. It never explains the difference in power between OWNER, EDITOR and VIEWER, which would have been the one piece of added value available.

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 states a concrete verb+resource ('Give a workspace member access to a Stride project') and enumerates the granted roles, so the action is unambiguous. It does not distinguish itself from the close sibling stride.update_project_member_role, and in fact its 're-running with a different role changes the role' line blurs that boundary.

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?

'Projects are invite-only by default, so this is what lets someone open the project' gives a clear condition for reaching for this tool. It stops short of explicit exclusions, e.g. that an existing member's role should be changed via update_project_member_role rather than here.

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