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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the description is not carrying the safety burden. It still adds genuine value by spelling out the access consequences, the default role, and the role-change-on-rerun behavior. It omits who is permitted to grant OWNER (privilege escalation concerns), which would matter for a permission-granting tool.

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 sentences, each front-loaded with its most decision-relevant fact: the action and role set first, the practical meaning second, the idempotency contract last. No filler and nothing 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?

For a three-parameter mutation with full schema coverage and annotations covering safety and idempotency, the description supplies what the structured fields cannot: why the tool exists and what it unlocks. Only the return value / error cases (unknown member, insufficient permission) are unaddressed, and there is no output schema to defer to.

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% and already documents projectId, member (UUID or email), and the role enum with its EDITOR default. The description's restatement of the role values and default duplicates the schema rather than adding semantics. Baseline 3 applies since the schema does the heavy lifting.

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 (give access / add member), the resource (Stride project), and the scope of the grant (role: OWNER/EDITOR/VIEWER with EDITOR default). It also explains the concrete effect — opening the project, being assigned work, being @-mentioned — which distinguishes it from the many story/document siblings.

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 context for when this tool is needed (projects are invite-only by default, so this is the mechanism that grants entry) and an explicit idempotency rule covering the re-invocation case. It does not name the neighboring alternatives stride.update_project_member_role or stride.remove_project_member, which is a real gap given how close the former is.

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