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

Annotations already declare it is a non-destructive, non-idempotent write. The description adds meaningful behavior: open communities admit immediately, approval communities forward the request, and invite-only communities require an invite link. It also states the prerequisite 'Requires a connected account,' which is not in annotations. It stops short of describing error handling or the exact response shape.

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?

The description is a single, front-loaded sentence that uses semicolons to pack in the three community-type behaviors and the auth prerequisite without any wasted words. It is appropriately sized and easy to scan.

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 single-parameter tool with no output schema and no annotations beyond safety hints, the description covers the action, the conditional outcomes, and the account prerequisite. It does not describe the immediate return value (e.g., whether a membership object or a pending request is returned), but the behavioral outcome is sufficiently clear.

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% and the only parameter, community_id, is never mentioned or explained in the description. While the parameter name is fairly self-explanatory, the description fails to compensate for the lack of schema documentation, leaving no added meaning about the parameter's format, source, or constraints.

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 states a specific verb and resource ('Join a community yourself') and distinguishes self-joining from organizer-facing siblings like approve_join_request. It also breaks down the three community types, so an agent can immediately tell what the tool does and in which scenarios it applies.

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 description gives clear context: use this when joining a community yourself, with behavior varying by community type (open, approval, invite-only). It does not explicitly name alternative tools or say when not to use this one, but the context and the word 'yourself' sufficiently separate it from organizer actions.

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