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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It says nothing about pagination (despite a 'min_time' parameter hinting at it), rate limits, output format, or whether it requires special permissions. The single word 'Following' provides zero behavioral insight.

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 short, which is not genuine conciseness but under-specification. It has no structure, no summary, and wastes the opportunity to convey essential information in a few more words.

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 lack of annotations and output schema, the description must compensate but does not. The tool likely returns a following list with pagination, yet nothing in the description explains the response shape, pagination flow, or any constraints. It is completely inadequate for effective tool selection and invocation.

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 schema covers 100% of parameters with descriptions, so the baseline is 3 even though the tool description adds no parameter information. The 'min_time' parameter description mentions pagination, but the tool description does not reinforce or add meaning 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 is a single word 'Following', which merely restates the tool name and gives no verb or resource context. It does not clarify whether this retrieves a user's following list, a follow action, or a category, and it fails to distinguish from the sibling tool scrapecreators_followers.

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?

There is no guidance on when to use this tool or when to prefer alternatives. The description provides no context about prerequisites, typical use cases, or how it differs from other scrapecreators tools.

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