Image Sync

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose meaningful traits: copying is transactional, only missing files are copied under a namespaced name, and noise entries are skipped unless copy_noise=True. It omits conflict/overwrite behavior, whether anything in collection.media is ever removed, and whether apply=True is reversible, which matters for a write-capable tool with no annotation safety profile.

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?

Two compact sentences, front-loaded with the read-only check and then the conditional write behavior. The parenthetical about namespaced naming earns its place. Little waste, though a short enumeration of the undocumented parameters would have been a better use of space than nothing.

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?

An output schema exists, so return values need not be described, which lowers the burden. Still, for a five-parameter tool with zero schema description coverage and no annotations, three parameters remain unexplained and the mutation path lacks any safety or side-effect framing, leaving the definition adequate but incomplete.

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, and it only explains two of five parameters (apply and copy_noise). catalog_path, only_filenames, and collection_media_dir receive no explanation at all; notably only_filenames is a free-form string with an empty default, and its expected syntax (comma-separated list, glob, exact names) is completely undefined anywhere.

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 uses specific verbs and resources: it checks consistency between a catalog and Anki's collection.media, and optionally copies missing files. That is a clear, concrete purpose. It does not explicitly contrast itself with near-siblings such as image_report or image_candidates, so an agent must infer the boundary rather than being told it.

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 dry-run versus apply split is implied well: without apply it only checks, with apply=True it copies. The copy_noise flag also gets a conditional. However, there is no explicit statement of when to prefer this tool over the other image/deck tools in the family, and no prerequisites or safety guidance before running with apply=True.

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