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

With no annotations and no descriptive text, the tool's behavior is entirely undisclosed. There is no information about read-only nature, pagination behavior, response format, or any side effects, which is a significant gap for a scraping tool.

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 under-specified to the point of being a single word. This is not efficient conciseness but rather a lack of substance, providing no actionable information for the agent.

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 tool with four parameters, no output schema, and many closely related sibling tools, a one-word description is completely inadequate. The agent has no way to understand the tool's scope, return values, or relationship to other followers-related tools.

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 descriptions cover all four parameters (trim, handle, user_id, min_time) with clear meanings, including pagination hints. Since schema description coverage is 100%, the baseline of 3 is appropriate even though the tool description itself adds no parameter information.

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 'Followers' merely restates the tool name without specifying an action or resource. It does not indicate that this tool retrieves follower lists for a TikTok handle, nor does it distinguish itself from sibling tools like scrapecreators_following.

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 on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer context from the tool name alone.

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