vk_groups_get_by_id

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

With no annotations provided, the description carries full burden but only states it 'gets' info, implying a read-only operation. It lacks details on permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this minimal disclosure is inadequate, leaving behavioral traits like authentication needs or data scope unspecified.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and avoids redundancy. Every word earns its place, making it highly concise and well-structured for quick understanding.

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 no annotations and no output schema, the description is incomplete for a tool with 2 parameters. It doesn't cover response format, error cases, or behavioral constraints. While schema coverage is high, the lack of output and behavioral context makes this insufficient for effective agent use, especially in a sibling-rich environment.

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 description coverage is 100%, so parameters are documented in the schema. The description adds marginal value by implying 'ID or short name' relates to group_ids, but doesn't explain field options or usage nuances. Baseline 3 is appropriate as the schema handles parameter documentation, with the description providing minimal extra context.

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 verb 'Get' and the resource 'community info', specifying it works 'by ID or short name'. It distinguishes from siblings like vk_groups_get (which likely lists groups) by focusing on specific community lookup, though not explicitly named. However, it doesn't fully differentiate from vk_users_get which might also get user info by ID.

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 like vk_groups_get or vk_users_get. The description implies usage for retrieving community details but doesn't specify contexts, prerequisites, or exclusions. It's a basic functional statement without comparative or situational advice.

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