link_to_community

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description's real added value is disclosing the dual-mode behavior (attach vs. detach), which the annotations do not express. It says nothing about required permissions or the effect of detaching on existing members.

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?

A single compact sentence, front-loaded with the primary operation and the inverse flagged via `unlink`. No wasted text, though the parenthetical inline backtick reference is slightly terse.

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?

A four-parameter mutation tool with only 25% schema coverage and no annotation explanation of the `account` parameter. The output schema exists so return values need not be described, but the description leaves the target-account semantics and prerequisite conditions entirely undocumented.

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 only 25% and the description effectively covers one parameter (`unlink`), whose meaning the schema already states in its own description. The `community`, `group` and especially the un-nullable `account` parameters get no added meaning from the description, so it fails to compensate for the sparse schema.

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 names a specific verb pair and resource: attach an existing group to a community, or detach it. An agent can tell what the tool does. It does not differentiate itself from siblings like update_group or update_group_participants, which mention nothing about communities.

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?

No when-to-use guidance is given. It clarifies that `unlink` selects the inverse operation, but never states when to call this instead of update_group or the other group-management siblings, nor any prerequisites (e.g. that the group must already exist and be owned/administered).

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