group_leave

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

With no annotations provided, the description carries the disclosure burden, and it does disclose the irreversible by-bot nature of the action. However, it does not explain the effect on the bot's membership, whether any permissions are needed, or what the response or error behavior looks like.

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, front-loaded sentences with no filler. The core purpose comes first, followed by the conditional requirement and the consequence, so an agent can parse the constraints quickly.

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 action, the description covers the main decision points: purpose, mandatory confirmation, and irreversibility. It is not fully complete because jid is not semantically defined and there is no indication of return values or failure states, but the essential call constraints are present.

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 compensate. It adds critical meaning to confirm (must be true despite its schema default of false), but it never explains that jid is the group identifier or what format is expected, leaving an essential parameter under-specified.

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 uses a specific verb-resource pair, 'Leave a group,' immediately identifying the action and target. It distinguishes the tool from sibling read-only group tools like group_metadata and list_groups, and no sibling overlaps with leaving a group.

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 explicitly states a precondition ('Requires confirm=true') and a key consequence ('Cannot be undone by bot'). It does not explicitly name alternatives or when-not-to-use, but no sibling offers a leave capability, so the conditional guidance is sufficient.

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