vk_wall_get_by_id

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

No annotations provided. The description only states it returns a list, implying a read operation but fails to disclose any behavioral traits like rate limits, authentication needs, or side effects.

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?

Single sentence, no fluff. Front-loaded and efficient.

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 4 parameters, no output schema, and no annotations, the description is too sparse. It doesn't explain return format, pagination, or error handling, leaving gaps for an agent.

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 75%. The description adds minimal meaning beyond schema; 'by their IDs' relates to the posts parameter but doesn't significantly enhance understanding. Baseline 3 is appropriate.

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 'Returns a list of posts from user or community walls by their IDs' clearly states the function with specific verb (returns) and resource (posts by IDs). It distinguishes from siblings like vk_wall_get and vk_wall_search which retrieve posts differently.

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. For instance, it doesn't note that it's for fetching specific posts by ID as opposed to vk_wall_get which might retrieve all wall posts.

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