vk_groups_get_addresses

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

No annotations are provided, and the description only states 'returns a list,' without disclosing behavioral traits such as whether it is read-only, possible rate limits, or any side effects. The agent cannot infer safe usage or constraints.

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, making it concise, but it lacks structure and additional context. It front-loads the purpose but misses opportunities to include usage hints or parameter relationships. It is adequate but not exemplary.

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?

With no output schema, the description should hint at return values or structure. It does not. The tool has 7 parameters and no annotations, yet the description is minimal. An agent would need to guess at the response format.

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 already describes 6 of 7 parameters (86% coverage), so the description adds no additional parameter meaning. The missing description for 'address_ids' is not compensated. Baseline 3 is appropriate given high schema coverage.

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 function is to 'return a list of community addresses,' which is specific and distinct from sibling tools like vk_groups_get_members or vk_groups_get. However, it could benefit from specifying the source (e.g., VK API group addresses).

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. For instance, users might wonder when to use this over vk_groups_get or other listing tools. The description lacks any context about prerequisites or common use cases.

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