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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description adds genuinely non-obvious behavior beyond them: following a manager cascades to its team and surfaces in the activity feed with following=true. It does not say whether re-following is a no-op or what is returned, which keeps it short of a 5.

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?

Two sentences, front-loaded with the action and followed by the one non-obvious semantic detail. No filler; the parenthetical about following=true is terse but earns its place by tying the behavior to feed filtering.

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 low-complexity, two-parameter toggle with full schema coverage and annotations present, so little prose is needed, and no output schema means return values need not be described. The cascade behavior is covered; only edge behavior (re-following, unfollowing a manager) is left implicit.

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%, so both the handle and the on flag (documented as 'false to unfollow') are already explained in the schema. The description mirrors that toggle concept but adds no format, casing, or validation detail beyond it – baseline 3 applies.

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 pair and resource (follow/unfollow an account) and adds a scoping nuance: following a manager pulls in its whole team into the activity feed. That distinguishes it from generic social-graph tools and from activity-reading siblings, though it never names an alternative tool directly.

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 by the statement of what the tool does, but there is no explicit when-to-use/when-not guidance and no routing to alternatives (e.g., reading the feed via activity vs. mutating follow state). For a simple toggle tool this is adequate, but the agent must infer the context.

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