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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds no behavioral context of its own: it doesn't say whether membership is permanently removed, whether messages/history are affected, whether re-joining is possible, or whether ownership transfer/constraints apply. With annotations carrying the burden, this is a low but non-contradictory score.

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?

A single short, front-loaded sentence with no filler. It is efficiently sized, though the brevity reflects under-specification rather than discipline.

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 destructive, irreversible-feeling mutation with one undocumented parameter and no output schema, the description says nothing about consequences, return values, or error conditions (e.g., not a member). Annotations cover safety hints but the agent still lacks the operational detail needed to invoke 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 0%, so the description must compensate and it does not — group_id is never mentioned, nor is its expected format (ID vs. name vs. slug). Only the phrase 'group chat' indirectly hints that group_id identifies the target group.

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 and resource ('Leave a group chat'), which distinguishes it from write-ish siblings like create_group, invite_to_group, and accept_group_invite. However, it largely restates the tool name and adds only the word 'chat' as new information, so it sits at the minimum-viable level rather than a sharp, differentiated statement.

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 when-to-use guidance, no mention of prerequisites (e.g., must be a member), and no routing toward alternatives such as decline_group_invite (for invitations) versus leaving a group you already belong to. The agent must infer everything from the name alone.

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