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

Annotations already declare idempotentHint=true and destructiveHint=false, so 'Audited and idempotent' partly repeats structured data. The description does add value beyond annotations: the owner/admin auth requirement and the explicit non-effects (no permission changes, no invites, no question assignment, no emails) tell the agent the blast radius of the write.

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?

Four short sentences, all front-loaded with the action and target before the constraints. The only mild waste is 'idempotent', which the annotation already asserts, but nothing is bloated.

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 no output schema and 6 required parameters at 17% description coverage, the description covers authorization, idempotency and non-effects well but omits what a revision mismatch produces (conflict handling) and what userId denotes. Adequate for the mutation itself, incomplete for correct invocation.

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 only 17% (just idempotencyKey), so the burden falls on the description. It ties membershipId/expectedRevision to prior returned values and maps 'business function and expertise' to jobFunction/expertise, but leaves userId completely unexplained (actor vs. target) and gives no format or value guidance for jobFunction/expertise. Partial compensation only.

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?

Specific verb+resource: 'Set a current Team/Enterprise member's business function and expertise'. Scope is bounded ('current Team/Enterprise member'), and the closing sentence enumerates what the tool does not do (permissions, invites, questions, emails), which implicitly separates it from the invitation and membership siblings. No sibling is named explicitly, so it stops short of a 5.

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?

States the authorization prerequisite clearly ('Requires a current workspace owner or administrator') and implies a read-first flow by saying the update targets 'the returned membershipId and revision'. Exclusions give negative guidance. No alternative tool is named for the same outcome, so it is clear context rather than full when/when-not/alternatives.

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