users_list_followers

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

Discloses caching for 10 minutes, which is helpful. However, with no annotations, the description does not cover authorization needs, rate limits, or other behavioral traits. It adds some value but lacks completeness.

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 concise with bullet-pointed tips and examples. It front-loads the main purpose. Minor redundancy in 'Common use cases' section but overall efficient.

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 the simplicity of the tool (one parameter, no output schema), the description provides basic purpose, caching info, and an example. However, without output schema, it does not describe the response format fully, which is a gap.

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 covers 100% of parameters with a description for 'id'. The description includes a concrete example ({"id": 123}), which adds context. However, no further explanation of the parameter 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 clearly states 'List followers of a user' and explains it returns users following the specified user. However, it does not explicitly differentiate from sibling tools like deals_list_followers or persons_list_followers, though the context of 'user' is understood.

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 like 'Shows users tracking this user's activities' and a common use case example, but does not mention when not to use this tool or suggest alternatives such as users_list for listing all users.

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