follow_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Follow a list' implies a write/mutation operation (changing follow state), but the description doesn't mention authentication requirements, rate limits, side effects (e.g., notifications), error conditions, or what happens on success. For a mutation tool with zero annotation coverage, this represents a complete lack of behavioral 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 extremely concise at just three words, with no wasted language. However, this brevity comes at the cost of being under-specified rather than efficiently informative. While front-loaded (the entire description is the core action), it lacks the necessary elaboration for a mutation tool.

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?

Given this is a mutation tool with no annotations, 0% schema description coverage, and an output schema (which reduces need to describe returns), the description is incomplete. It doesn't address authentication needs, error cases, side effects, or parameter meaning. While the output schema might document return values, the description fails to provide essential context for safe and correct usage.

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 input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information about 'list_id'. The description 'Follow a list' doesn't mention the parameter at all, offering no compensation for the schema gap. It doesn't explain what a list_id is, where to find it, or format requirements, leaving the parameter completely undocumented.

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 'Follow a list' is a tautology that essentially restates the tool name without adding meaningful context. It specifies the verb 'follow' and resource 'a list', but doesn't clarify what 'following a list' means operationally (e.g., subscribing to updates, adding to feed). While it distinguishes from obvious non-siblings like 'delete_tweet', it doesn't meaningfully differentiate from close siblings like 'unfollow_list' beyond the opposite action.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing authentication, list accessibility), appropriate contexts, or relationships with similar tools like 'follow_user' or 'pin_list'. The presence of 'unfollow_list' as a sibling suggests a toggle relationship, but this isn't explicitly stated in the description.

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