cached_user_group_memberships_delete

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

The description discloses an important behavioral requirement: it requires 'Delete' permission on 'Security'. Since no annotations are provided, this is valuable context. However, it does not mention whether the deletion is permanent, idempotent, or how errors or non-existent memberships are handled.

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 a single concise sentence followed by a necessary permission note. Every word contributes meaning, and the core action is front-loaded.

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 simple two-parameter delete operation with no output schema, the description is largely sufficient: it names the action, the affected entities, and the required permission. It could be more complete by clarifying the distinction from remove_groups_for_user or noting cache side effects, but these are minor gaps given the tool's simplicity.

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 schema provides only type information for userId and groupId, so the description must compensate. It does clarify that the operation involves a 'user' and a 'group', which maps naturally to the two parameters. Still, it adds little beyond the parameter names and does not explain identifier formats, constraints, or behavior when either ID is invalid.

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 states a specific action and resource: 'Remove the membership between a user and a group.' It also distinguishes itself from sibling operations like add or get by explicitly describing deletion, making the tool's purpose immediately obvious.

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 intended use is inferable from the action 'Remove', and the permission requirement provides some operational context. However, the description does not explicitly state when to use this tool versus alternatives such as cached_user_group_memberships_remove_groups_for_user, nor does it describe exclusions or preferred scenarios.

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