vk_friends_get

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

States 'access level: read', implying read-only behavior. However, with no annotations, it misses important details like pagination, default count (5000), and nuance between ID-only vs. detailed results based on the 'fields' parameter.

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?

Brief and mostly to the point, but includes redundant info like 'VK API method: friends.get' and 'Tool name: vk_friends_get' that could be omitted.

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?

Adequate for a simple tool, but lacks explanation of parameter relationships (e.g., 'fields' toggles between ID-only and details) and pagination behavior. No output schema adds to incompleteness.

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 coverage is 86%, so most parameters are described. The description adds little beyond schema, mentioning 'user IDs or detailed information' which relates to 'fields' but doesn't provide new semantics.

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 user IDs or detailed information about friends, and mentions the VK API method. However, it does not differentiate from sibling tools like vk_friends_get_online or vk_friends_get_mutual, leaving some ambiguity.

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 on when to use this tool versus alternatives (e.g., vk_friends_search, vk_friends_get_online). The description lacks explicit when-to-use/when-not-to-use instructions.

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