Block / unblock in a group

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

Adds real behavioral context beyond annotations: the blocked user leaves the group and cannot join or add. Combined with the permission note, this tells the agent the blast radius of the destructive action. It does not describe reversibility beyond 'lifts the block' or any side effects on existing content.

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?

One sentence, front-loaded with the actor permission, no filler, and the essential effect in a compact parenthetical.

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 mutation with no output schema, the description covers who can call it and the practical effect. It falls short on the boolean parameter semantics and on whether unblocking restores prior membership state.

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 clarify the three parameters. It implies group_id and user_id contextually, but never states the critical mapping of the boolean 'block' parameter (true = block, false = unblock), leaving the most important parameter ambiguous.

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?

States a specific verb and resource ('blocks a user from a group ... or lifts the block'), making the toggle nature clear. It is distinguishable from siblings like group_member_role and group_approve, though it does not explicitly contrast with them.

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?

'Owner and editors' gives a prerequisite, which is useful, but there is no explicit guidance on when to use this versus group_member_role or group_approve, nor any when-not conditions.

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