vk_put_migratio_da506ec8aeb9

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

The description discloses technical details: multipart form data, file object shape with filename/contentBase64/contentType, array support, field aliases, and required authentication. However, it does not disclose behavioral consequences such as whether the import overwrites existing data, is idempotent, or returns a status; with no annotations, this is a moderate gap.

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 purpose and contains many useful details, but the first and third sentences redundantly restate the import scope ('Import all projects, tasks etc.' vs 'Imports all projects, tasks, notes...'). Overall it is still 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?

The tool has no annotations and no output schema. The description covers input construction and auth, but does not explain return values, whether the migration is asynchronous, or potential side effects like duplicates. For a one-parameter but complex multipart import, this leaves some gaps.

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 input schema only defines a 'form' object with a brief description. The description adds substantial meaning: multipart form data structure, file object schema, multi-file arrays, top-level path/query handling, and camelCase/snake_case aliases, plus the required 'import' field.

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 it imports all projects, tasks, notes, reminders, subtasks and files from a TickTick backup export into Vikunja, and names the exact REST endpoint PUT /migration/ticktick/migrate. This is a specific verb+resource+scope and distinguishes from sibling migration tools by explicitly identifying TickTick.

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?

It says to pass multipart form data with an 'import' field, and notes that authentication is required. This gives clear context for when to invoke (when a TickTick backup is available) but does not explicitly contrast with alternative migration tools or mention when not to use it.

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