remove_item_member

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Remove an item member' and does not disclose that this is a destructive/write operation, that confirm must be true, whether removal is reversible, or what permissions are needed. The confirm requirement appears only in the schema, not in the description.

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 extremely short and contains no wasted words, so it is concise. However, it is so under-specified that it adds little value beyond the tool name, bordering on a tautology rather than a genuinely informative 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?

This is a destructive mutation tool with no annotations and no output schema, yet the description omits critical context such as the confirm flag behavior, effects of removing a member, and any permission or safety caveats. The schema explains the parameters, but the description fails to provide the operational context an agent needs to invoke it confidently.

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%, with each parameter (shareId, memberShareId, confirm) already having a meaningful description. The tool description itself adds no parameter-level meaning, so the baseline of 3 applies: the schema does the heavy lifting.

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 names a specific verb ('Remove') and a clear resource ('item member'), which distinguishes it from related tools like remove_vault_member and update_item_member. It is slightly terse and essentially restates the tool name, but the meaning is unambiguous enough for an agent to select it for removing a member from an item's sharing list.

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?

There is no guidance on when to use this tool versus alternatives such as list_item_members, update_item_member, or remove_vault_member. The description provides no context about prerequisites, ownership requirements, or situations where removal would be inappropriate.

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