Join groups and handle join requests

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

Annotations already flag it as a write-capable, non-idempotent, open-world tool. The description adds real behavioral context beyond them: the admin prerequisite, the surprise that `join` may silently become a pending request, and per-action result semantics ('Returns the group id', 'Each result says whether it worked').

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?

Front-loaded summary sentence followed by a tight action list; each bullet earns its place by naming the action and its outcome. Slightly verbose in the opening clause but no wasted content.

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 an 8-parameter multi-action tool with no output schema, the description covers every action's purpose and the key gating conditions (admin, approval). Return values are only loosely described, but no output schema exists to compensate, so this is close to complete.

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 100%, so the schema already documents each parameter and its required actions. The description adds only marginal meaning (which action maps to which concept) beyond that baseline.

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 resource (groups) and enumerates the exact five operations (preview_invite, join, list_requests, approve_requests, reject_requests). An agent can distinguish this from siblings like add_group_participants or get_group_invite_link without opening the schema.

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?

Explains the context for each action, including that joining an approval-gated group becomes a pending request and that list/approve/reject require the account to be an admin. It does not, however, name any alternative tool or give explicit when-not-to-use guidance.

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