sync_lists

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

Given no annotations, the description provides some behavioral context: it backs up the master, imports missing names, and avoids touching LKP-VN.OSN. However, it fails to clarify direction of sync (one-way vs two-way), error handling, or auth requirements.

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 concise, with the purpose front-loaded. It uses bullet-like structure for details, but the Russian text and jargon reduce accessibility.

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 5 parameters and no output schema, the description fails to explain root and master, and omits output or side effects beyond backup. This leaves significant gaps for safe 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?

Schema description coverage is 0%; description explains only the open_only parameter. Key parameters like root and master are unexplained, and resolved_ids/open_ids lack format constraints.

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 the tool syncs two ID lists with a catalog, using specific verbs like 'import' and 'move'. It clearly indicates the resource (lists) and action (sync), though domain jargon (LKP, master) may reduce clarity. It does not differentiate from siblings like reconcile_by_name.

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 versus alternatives. The description only explains the open_only flag but does not specify prerequisites, contexts, or when not to use.

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