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

Annotations already mark readOnlyHint=false, idempotentHint=true, and destructiveHint=true. The description adds useful behavior: audited, permission requirement, and negative side-effect exclusions. This goes beyond the annotation flags and describes the operational context, meriting a strong score even though some details like rate limits or failure modes are not discussed.

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?

Every sentence delivers distinct value: 1) what operation is done, 2) who may execution it, 3) behavioral characteristics and exclusions. Content is compiled front-loaded with the definition of the resource and the required revision, without any wasted words.

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?

The description covers prerequisites, permission, idempotency, audit, and non-side-effects. However, there is no output schema, and the description doesn't clarify expected return semantics, failure modes, or whether the operation overwrites existing expertise/jobFunction values. For a complex mutation with 6 required parameters and no return schema, this is the main gap. Given the strong annotation and idempotency details in the schema, it remains acceptable but not fully complete.

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 only 17%, so the description must compensate. It partially does: it maps jobFunction to 'business function', expertise to 'expertise', membershipId to 'returned membershipId', and expectedRevision to 'revision'. This interpretation helps, but it leaves userId unexplained, the relationship between userId and membershipId unclear, and does not describe how expertise array values are formatted or updated (e.g., replaced vs appended).

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 clearly names the action (set), the resource (a Team/Enterprise member's business function and expertise), and the specific keys required (returned membershipId and revision). It also distinguishes from sibling tools by explicitly negating side effects like changing permissions, inviting people, assigning questions, or sending emails, which separates it from many adjacent workflow tools without needing to name them.

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?

It conveys when to use the tool: when you already have a membershipId and expectedRevision and need to set business function/expertise, and only if you are an owner or admin. It also gives clear exclusions of non-goals such as inviting or emailing. However, it does not explicitly name alternative tools, so just below the full 5.

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