agent_set_follow

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates a mutating action ('follow or unfollow'), but it does not disclose side effects, reversibility, permissions, or what happens when unfollowing. The phrase 'extra notifications' offers minimal behavioral context but falls short of full transparency.

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, front-loaded sentence that conveys the core action and purpose without extraneous words. It is appropriately concise for the tool's simplicity.

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?

Despite having an output schema and three parameters, the description is too sparse. It does not explain parameter mapping, behavior for true/false values, error conditions, or return values. For a mutation tool with no annotations, this level of completeness is inadequate.

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 0%, and the description does not compensate by explaining any parameter semantics. It does not explain conversation_id, followed_participant_id, or the 'following' boolean, leaving the agent without guidance on how to populate these fields 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 clearly states the action (follow/unfollow), the target (one Agent in a shared room), and the purpose (extra notifications). It distinguishes itself from sibling tools like agent_following, which likely queries follow status rather than setting it.

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 implies usage context: to manage notifications for an agent in a shared room. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it or any exclusions.

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