vk_fetch_all

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already covered. The description adds useful context: the max_items hard cap to protect context, automatic array-path detection, and the supported pagination styles. However, it doesn't disclose rate-limit behavior, error handling on mid-pagination failures, or what happens when truncated=true.

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?

Front-loaded with the core action, then structured Args section explaining each parameter, then a Returns line. Efficient and well-organized. The Returns line could be considered slightly redundant given an output schema exists, but it adds concrete field names in one compact sentence.

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 an output schema present, the description needn't explain return values in depth, yet it does list the return fields concisely. The parameter explanations cover all 7 params despite 0% schema coverage. The only gap is lack of explicit guidance on error handling during pagination and what 'truncated' means operationally.

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 0%, so the description must compensate. It provides meaningful semantics for each parameter: operation_id is 'a read endpoint from the catalog,' items_path overrides the default array path, limit is page size, max_items is a hard cap with default 10000. This adequately compensates for the empty schema descriptions across all 7 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?

States a specific verb+resource: 'auto-paginate a read endpoint and return every row in one response.' This clearly distinguishes it from the sibling vk_call_method, which presumably calls a single page. No explicit sibling differentiation by name, but the pagination-oriented purpose is unambiguous.

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?

The description implies usage (when you need every row, use this instead of single-call alternatives) but never explicitly says 'use this instead of vk_call_method when you need all pages' or states exclusions. The parenthetical '(cursor fields are managed)' hints that some arguments are off-limits, but no explicit when-not guidance is provided.

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