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

Annotations already declare idempotency and non-destructiveness; the description goes further by explaining how the idempotency is achieved (reuse an unchanged request_id) and by disclosing dual auth paths plus a secret-handling warning. It does not describe failure modes (invalid code, already a member) or the response shape, so it stops short of full disclosure.

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 with purpose, then safety and auth notes in short imperative sentences. The security admonition is repeated nearly verbatim in both the description and the key field, which is mild redundancy, but overall the text is tight.

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 3-parameter mutation with no output schema, the description covers the critical unknowns: idempotent retry semantics, credential options, and secret hygiene. It omits error/success outcomes and membership edge cases, which an agent would benefit from knowing.

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 coverage is 100% and every assertion in the description (invite_code is secret, request_id is a stable reuse-for-retry id, key is an alternative to the Bearer header) is already present in the schema field descriptions. Baseline 3 is appropriate since the schema does the heavy lifting and the prose adds little new per-parameter semantics.

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 ('Join a private community') and names the gating input (invitation code). It does not, however, differentiate itself from the sibling 'join' tool or the cluster of community_* tools, leaving a possible ambiguity an agent must resolve on its own.

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?

'Use a stable request_id for safe retries' is genuine operational guidance, and the auth note tells the agent which credential path to use. But there is no explicit when-to-use-this-vs-alternative statement (e.g., community_join vs join, or when a user lacks an invite code), so routing is only implied.

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