vk_users_get_followers

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

No annotations provided. The description discloses return type (IDs) and sorting (by date, most recent first). It does not mention potential errors, rate limits, or that requesting fields may change the output structure. Adequate but not rich.

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?

One sentence that clearly and concisely states the purpose and sorting. No wasted words; optimal length.

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?

The description covers the key behavior (returning IDs, sorted). With 5 parameters and no output schema, it provides enough context for an agent to understand the tool's function. Missing slight details like pagination effect, but schema covers param ranges.

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 description coverage is 100%, so baseline is 3. The description adds context about sorting but does not elaborate on parameter behavior beyond what the schema provides. Acceptable but no significant extra value.

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 tool returns a list of follower IDs, sorted by date added. It distinguishes from siblings like vk_friends_get (friends) and vk_users_get_subscriptions (subscriptions) by focusing on 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?

The description implies when to use this tool (to get followers) but does not explicitly state when not to use it or compare to alternatives like vk_friends_get or vk_users_get_subscriptions. No exclusions are provided.

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