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

With no annotations supplied, the description carries the full burden and it does add genuinely non-obvious behavior: a hard cap of 5 active memberships, a 7-day post-leave cooldown, and an idempotent-style response ("joined:false") when already a member. It does not mention authentication requirements or whether the join is immediate or pending approval, which is the main remaining gap.

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?

Three short sentences, front-loaded with the core action and followed by the two constraints that actually affect the decision to call. Nothing is redundant or padded.

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 two-parameter mutation with no annotations and no output schema, the description covers the action, the key constraints, and one response outcome, which is enough to call it correctly. It could go further by describing the success response shape or auth expectations, but the essentials 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 100%, so both parameters are already fully documented in the schema, including the grp_/slug format and the api_key usage warning. The description's mention of "by id or slug" merely restates the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource ("Join a group") and states the key identifier forms (id or slug), so an agent can immediately tell this apart from create_group, get_group, or leave_group by the verb alone. It stops short of explicitly naming those siblings, which keeps it at a 4 rather than a 5.

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?

The membership cap ("Up to 5 active memberships") and cooldown ("7-day cooldown applies after you leave") give practical context for deciding whether joining is possible, but there is no explicit routing guidance such as when to use create_group instead or what happens if the cap is hit. Usage is implied rather than spelled out.

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