Join / leave group

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

Annotations already mark this as destructive, non-idempotent, and open-world, so the baseline is lower. The description adds the useful owner-cannot-leave constraint, but does not explain membership prerequisites, approval behavior, permissions, or side effects beyond the basic join/leave action.

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?

Two short sentences, front-loaded with the primary action and then the boolean mapping and owner restriction. No wasted text.

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?

Annotations cover safety traits, but for a group-membership mutation the description omits prerequisites such as whether the caller must already be a member, whether approval is required, and what happens on failure. It is adequate but incomplete for a destructive group tool.

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 0%, so the description must carry parameter meaning. It fully explains the join boolean semantics, but group_id is left implicit even though its purpose is obvious from the tool name and schema.

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 states a specific verb and resource, and explains that the same tool both joins and leaves via the join boolean. It clearly separates the two operations but does not differentiate itself from nearby group-management siblings such as group_member_role or group_approve.

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?

It explains how to invoke join vs leave through join=true/false, and gives one important conditional rule: the owner cannot leave. It does not say when to use this instead of related tools like group_approve, group_member_role, or group_block.

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