vk_friends_get_app_users

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the return format (list of IDs) and condition (friends who installed the app). However, it does not discuss authentication requirements, rate limits, or possible empty results. The description is 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?

The description is a single, short sentence that is front-loaded with the key information. Every word contributes meaning; there is no filler or repetition. It is maximally concise.

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 tool has no parameters and no output schema, the description covers the essential information: what it returns and the condition for filtering. It does not mention pagination or limits, but for a simple list of IDs this is sufficient. The description is almost complete for the tool's simplicity.

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 no parameters, and schema description coverage is 100%. Per guidelines, this yields a baseline of 3. The description adds no parameter meaning since there are none, but it is also not needed. Score is appropriate.

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 action ('Returns a list of IDs'), resource ('current user's friends who installed the application'), and distinguishes from sibling tools like vk_friends_get (all friends) and vk_friends_get_mutual (mutual friends). The verb 'returns' and specific condition make the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as vk_friends_get or vk_friends_get_mutual. It does not state when not to use it or which context is appropriate. Given the numerous sibling tools, this lack of guidance is a notable gap.

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