vk_users_get_subscriptions

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states what is returned, but does not mention that it is a read-only operation, potential side effects, pagination behavior, or permission requirements. It fails to disclose that the output can be extended or that fields can be requested.

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 sentence of 14 words, front-loading the core functionality. Every word is necessary and there is no redundant information. It is highly concise and well-structured.

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 5 parameters (offset, count, extended, fields) and no output schema, the description is insufficient. It does not mention pagination, the effect of the extended flag, or how fields modify the output. For a moderately complex API call, more context is needed to ensure correct 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?

Schema coverage is 80% (4 of 5 parameters have descriptions). The description adds no additional meaning beyond the schema; it does not explain parameters like offset, count, extended, or fields. For the undocumented 'fields' parameter, the description offers no clarification. Baseline 3 is appropriate as the schema does most of the work.

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 IDs of users and communities followed by the user', specifying the verb (Returns), resource (list of IDs of users and communities), and context (followed by the user). It distinguishes from sibling tools like vk_users_get_followers (returns followers) and vk_groups_get_members (returns group members).

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 is provided on when to use this tool versus alternatives. The description only states what it does, without mentioning prerequisites, typical scenarios, or exclusions. The user must infer usage from context.

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