update_membership

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. 'Update a membership' reveals nothing about whether the operation is destructive, what fields are changed, permission requirements, or side effects. It is completely lacking in behavioral transparency.

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 description is very short and not verbose, but it is under-specified to the point of being a restatement of the tool name. It does not offer any valuable information that would justify its existence as a standalone description.

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?

Despite having only two parameters and no output schema, the tool still requires basic operational context such as what fields can be modified, what the role values signify, and whether the update is partial or full. The description is wholly incomplete even for a minimal update operation.

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?

The input schema declares id (required) and role (enum), but the role parameter has no description, and the enum values alone provide limited meaning. The description adds no explanation of how role affects membership or what other fields might be updated. With schema coverage at 50%, the description fails to compensate for the gap.

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 'Update a membership' is a tautological restatement of the tool name. It does not specify what aspects of the membership can be updated (e.g., role), nor does it differentiate from sibling tools like update_membership_status which also update membership-related attributes.

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?

The description provides no context for when to use this tool versus alternatives. It does not mention any prerequisites, typical use cases, or exclusions. Sibling tools like update_membership_status exist, but the description gives no guidance on choosing between them.

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