vk_photos_get

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

The description only says 'returns a list' with no behavioral detail beyond that. Annotations are absent, so the description carries full burden. It does not disclose pagination, default behavior when no parameters are provided, or what the list contains (e.g., photo objects, metadata).

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 concise sentence, front-loaded with the core action. While appropriately brief, it could include more context without losing conciseness.

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 10 parameters, many siblings, no output schema, and no annotations, the description is too minimal to fully equip an AI agent. It lacks context on return structure, pagination, and selection criteria.

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 80% (8 of 10 parameters have descriptions). The tool description adds no parameter information beyond the schema. The baseline is 3 due to high coverage, and the description does not add meaningful value or compensate for the 2 undocumented parameters.

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 'returns' and resource 'list of user's or community's photos'. It directly conveys the main purpose but lacks differentiation from similar tools like vk_photos_get_all or vk_photos_get_by_id, which also return photo lists.

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 siblings. There are many photo-related tools (e.g., vk_photos_get_all, vk_photos_get_by_id) with no hints on selection criteria or prerequisites.

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