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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds real value by disclosing the effect of following (reply and status notifications) and that the operation is a reversible toggle, but says nothing about membership prerequisites, idempotency, or what unfollowing removes.

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 front-loaded sentence with no filler; the follow action and its user-visible benefit come first, with the unfollow case appended. The phrase 'where it stands' is slightly idiomatic but does not obscure meaning.

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?

An output schema exists, so return values need no explanation, and the two-parameter surface is small. Still, for a mutation tool the description omits prerequisites (must the user be a member of the community?) and any note on effects of unfollowing, leaving modest gaps.

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 only 50% — postId is documented ('from search_community') while the 'following' boolean is not. The description compensates by explaining that 'following' is a toggle where false means stop following, which is the key semantic an agent needs to set the parameter correctly.

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 gives a specific verb and resource ('Follows a post') and immediately clarifies that the same tool also unfollows ('or stops following it'). It is clearly distinguishable from sibling tools like vote_community_post or search_community, though it never names an alternative explicitly.

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?

Usage is implied rather than stated: the benefit clause ('so the user hears of its replies and where it stands') tells the agent why one would follow, but there is no explicit when-to-use/when-not guidance and no routing away from vote_community_post or search_community.

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