users_add_follower

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

Discloses the basic behavior ('Makes one user follow another user's activities') and outcome ('Follower will see activities of followed user') but omits details on authentication, side effects, or reversibility. No annotations exist to supplement this.

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?

Concise with clear sections (workflow tips, common use cases). The example JSON adds practical value. A single sentence could suffice, but structure aids readability.

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 tool with two parameters and no output schema, the description adequately covers purpose, usage context, and example. Slightly more detail on expected behavior would raise the score.

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% (both 'id' and 'user_id' described). The description adds an example JSON that clarifies parameter usage, but the schema already provides clear definitions. Baseline 3 is appropriate.

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 ('Add a follower to a user') and the effect ('Makes one user follow another user's activities'). It distinguishes itself from sibling tools like deals_add_follower by specifying 'user' but does not explicitly compare.

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?

Provides workflow tips ('Useful for team collaboration and visibility') and a common use case example, implying when to use the tool. However, it lacks explicit when-not-to-use guidance or comparison with alternative tools.

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