vk_photos_search

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

No annotations are present, so the description must disclose behavioral traits. It only mentions 'Access level: read', which is minimal. It does not disclose rate limits, pagination behavior, or any 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?

The description is very short and front-loaded with the main action. However, it includes redundant info like 'Tool name' and 'Section' which may not be useful for an AI agent. Could be slightly more concise.

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 9 parameters and no output schema, the description is incomplete. It does not explain how parameters interact (e.g., search query vs geolocation), pagination via offset/count, or the structure of the returned list. More detail is needed for a search tool.

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 78%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions; it does not elaborate on how parameters like 'q', 'lat', 'long' combine or on the meaning of 'sort' values.

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 states it returns a list of photos and indicates it's a search tool (via VK API method). This distinguishes it from non-search photo tools like vk_photos_get. However, it does not explicitly mention the types of search (text, geo) or scope.

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 vs sibling tools like vk_photos_search vs vk_photos_get. The description is generic and does not offer any usage context or exclusions.

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