batch_follow

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

Discloses authentication requirement and error handling behavior (continue or stop), which are key behavioral traits. However, does not mention return values or other side effects.

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 sentences, no unnecessary words, front-loaded purpose followed by constraints and behavior. Efficient and to the point.

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?

Covers the essential aspects for usage given no output schema, but could mention the return value (e.g., list of success/failure per user) to be fully complete.

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 description explains the 'continueOnError' parameter's effect and mentions the batch size for 'actors', but does not detail the format of actors (e.g., usernames or IDs), leaving some ambiguity.

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 verb 'follow' and the resource 'multiple users', distinguishing it from the singular 'follow_user' sibling by indicating it is a batch operation.

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 context on batch size (up to 25) and error handling mode via 'continueOnError', but does not explicitly compare to the singular follow_user tool or provide when-to-use guidance.

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