update_item_member

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states 'update' without revealing the write-confirmation requirement, permission needs, or side effects. The confirm parameter in the schema hints at the write nature, but the description itself adds no behavioral context beyond the verb.

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 one-sentence description is tightly worded with no filler, front-loading the core action. It earns high marks for conciseness, even though brevity sacrifices behavioral details.

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 mutation with a mandatory confirmation flag and several related sibling tools, a bare one-liner is not complete: it omits the confirm requirement, the relationship between shareId and memberShareId, and when to choose this over update_vault_member. The schema compensates for parameters, but the description lacks enough context for reliable tool selection.

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%, so every parameter already has a description in the schema. The description itself adds no parameter-level meaning beyond the schema, such as the confirm flag semantics or the role enum values.

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 an item member role' uses a specific verb (update), a precise resource (item member), and target attribute (role), clearly distinguishing it from siblings like update_vault_member and remove_item_member. No ambiguity remains about the tool's core function.

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 offers no guidance on when to use this tool versus alternatives such as update_vault_member or share_item. It also fails to mention that confirm must be true for the write operation to execute, which is critical usage information.

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