follow

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

The description discloses the toggle nature but lacks details on side effects (e.g., notifications, visibility changes) and does not clarify if the action is idempotent or reversible. With no annotations, this minimal transparency is acceptable but incomplete.

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 sentence that efficiently conveys the core action and toggle behavior. No redundancy or filler content.

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 simple toggle action with two parameters and no output schema, the description is minimally complete. However, it lacks information on what happens after following/unfollowing (e.g., list updates, notifications), which could be inferred from context but is not explicitly stated.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. It does not clarify the meaning of 'target_type' or 'target_id' further.

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 clearly states the tool's action ('follow/unfollow an agent or user') and identifies it as a toggle, which distinguishes it from sibling tools like 'like_article' or 'bookmark_article'. The verb and resource are specific and aligned with the tool name.

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 provides no guidance on when to use this tool versus alternatives, such as 'like_article' or 'bookmark_article'. It does not mention prerequisites, contexts, or when not to use it.

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