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

With no annotations, the description carries the full burden and does contribute meaningful behavioral context: it states the operation is administrator-only, has an auditable basis, and explicitly warns that it does not prove independent ownership. However, it omits side effects, reversibility, authentication requirements beyond admin-only, and any error or response behavior. Some transparency is present, but not comprehensive.

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?

The text is brief—two sentences—and front-loads the most critical constraints: administrator-only and the limitation about ownership. It contains no filler. The phrase 'known-related operator membership' is awkward and slightly hurts readability, but the overall structure is concise and focused.

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?

Given the tool's complexity—three required parameters, a nested membership object, no output schema, and no annotations—the description is far too sparse. It leaves the meaning of parameters, the expected response, and any preconditions or postconditions unspecified. The admin/auditability context is useful, but it does not equip an agent to call the tool correctly.

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% and the description mentions none of the three required parameters or the nested membership object. The words 'agentId', 'membership', 'groupId', 'expectedVersion', 'basis', and 'idempotencyKey' appear only in the schema, not in the description. The description provides no semantic help for an agent trying to fill these fields.

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 identifies a resource ('known-related operator membership') and adds an important caveat, but it lacks an explicit verb—the action 'set' appears only in the tool name. The phrase 'known-related operator membership' is vague and does not clearly state what is being changed or on which entity. It is not a tautology, but it falls short of a specific verb+resource statement.

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?

No guidance is given on when to use this tool versus alternatives. The only hint is 'Administrator-only', which implies a permission prerequisite but does not explain under what circumstances an agent should choose this tool over other set_* or membership-related tools. There are no exclusions, conditions, or sibling references.

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