vk_put_migratio_991857c055fb

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

With no annotations, the description carries full burden and does so thoroughly: it discloses the preview scope (first 5 tasks), multipart form data requirements, file object structure, multi-file arrays, parameter aliases, path/query field mapping, and authentication needs. This is comprehensive behavioral disclosure.

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 front-loaded with the core purpose ('Preview CSV import'), then delivers dense, useful details in six sentences. Every sentence contributes actionable information with no redundancy or fluff.

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's complexity (raw proxy, nested multipart object, no output schema), the description covers input encoding, required fields, aliases, auth, and preview behavior. The only minor gap is the format of the `config` string, but that is likely domain-specific and not essential for invocation.

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?

The schema already describes the `form` parameter in detail, and the description goes further by explaining aliases, top-level field mapping for path/query parameters, multi-file array handling, and required subfields (import, config). This adds significant value beyond the schema.

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 immediately states 'Preview CSV import' and gives the exact endpoint (PUT /migration/csv/preview), then clarifies it generates a preview of the first 5 tasks. This clearly differentiates it from other migration operations (import, list) and makes the tool's purpose 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 makes it clear the tool is for previewing CSV imports and notes that authentication is required. It implies it should be used before an actual import, but it does not explicitly name alternative tools (e.g., the import endpoint) or state when not to use it, so it lacks explicit exclusion guidance.

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