sync_collection

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

Annotations declare it as a non-read-only but non-destructive local operation, and the description adds real behavioral detail beyond them: incremental default behavior, what full=true additionally catches (removals, folder moves, edits), and that tracklists/countries come from a separate sibling. It stops short of mentioning failure modes or re-sync cost.

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?

Four compact sentences, front-loaded with the core action, then mode semantics, then usage ordering, then a related-tool pointer. Every sentence carries distinct information with no repetition.

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 no output schema, the description adequately covers what the sync produces conceptually, its two modes, and its prerequisite role. It could be more complete on error/partial-sync behavior, but nothing essential for correct invocation is missing.

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 coverage is 0%, so the description carries the burden for the single 'full' parameter, and it does so well: explaining that default is incremental and full=true re-reads everything and catches removals/moves/edits. Minor gap is that it doesn't describe the boolean's default in-line, though the schema supplies that.

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 (copy/sync) and resource (collection, folders, wantlist) plus the destination (local SQLite cache). It is immediately distinguishable from query_collection, collection_summary, and sync_release_details, which are named or clearly separate.

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?

Gives explicit ordering guidance ('Run this before using query_collection or collection_summary') and explains the incremental-vs-full choice. It doesn't state when not to use the tool, but the operational context is clear and actionable.

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