clear_memberships

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

The description indicates a destructive write operation but fails to disclose behavioral traits beyond what is minimal. Without annotations, it should mention side effects (e.g., if group becomes empty), permission requirements, reversibility, or impact on other entities.

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, well-structured sentence that is front-loaded with the action ('Remove all users') and the resource. It is appropriately sized and contains no unnecessary words.

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 absence of annotations and output schema, the description lacks completeness. It does not clarify the context of use, behavioral expectations, or what happens after removal, leaving the agent underinformed for a destructive 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 tool description adds no meaning beyond the schema's parameter description, which already explains 'group_id'. With schema description coverage at 0% (likely meaning tool description doesn't cover parameters), the description does not compensate.

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 'Remove all users from a permission group in Metabase' uses a specific verb ('Remove all users') and names the resource ('permission group'), clearly distinguishing it from sibling tools like 'delete_membership' (removes a single user) and 'add_membership'.

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 provided on when to use this tool versus alternatives such as 'delete_membership' or 'list_memberships'. It does not mention prerequisites, potential risks, or when not to use it.

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