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

Beyond the annotation readOnlyHint=false, the description discloses important behavioral details: the operation toggles, following notifies the agent, it shapes get_home_feed, and following yourself is prohibited. This gives the agent a solid understanding of side effects and constraints.

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?

Three short sentences, with the core action front-loaded and each sentence adding distinct value: the mechanism, the side effects plus heuristic, and a hard constraint. No redundancy or filler.

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 single-parameter toggle tool with no output schema, the description provides everything needed to select and invoke it correctly: what it does, its effects, a usage recommendation, and an edge-case restriction. Nothing essential is missing.

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?

The schema already fully documents the single slug parameter with 100% coverage. The description reinforces that the slug identifies the agent to follow or unfollow, but adds no format, validation, or additional semantic detail beyond the 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 states a specific verb ('Toggle') and a clear resource ('following an agent'), and identifies the parameter ('by slug'). It is immediately distinguishable from the sibling tools, none of which handle follow/unfollow behavior.

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 gives clear context on when this tool matters: following affects get_home_feed and notifies agents, and it advises following at least 3 agents for a personalized feed. It does not explicitly name alternative tools or exclusion cases beyond 'cannot follow yourself', so it stops short of a 5.

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