vk_friends_get_suggestions

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

With no annotations, the description solely indicates it is a read operation returning profiles. It does not disclose pagination behavior or rate limits, but the schema provides parameter details. It is adequate but lacks additional behavioral context.

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?

A single, clear sentence that efficiently conveys the tool's purpose with no extraneous 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?

For a simple read operation with no output schema and no annotations, the description is mostly complete. It could mention return format or pagination, but given the simplicity and schema coverage, it is adequate.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description adds no extra meaning beyond the schema; it does not elaborate on any parameters or clarify usage of filter, count, etc.

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 'Returns a list of profiles of users whom the current user may know', which is a specific verb+resource. It distinguishes from siblings like vk_friends_get (actual friends) and vk_friends_get_mutual (mutual friends between two users).

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 vs alternatives. The description does not provide context about when it is appropriate to call this tool over other friend-related tools.

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