pick_top

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

With no annotations, the description carries the full burden. It discloses folder creation, default sync behavior via scp, and optional NOTES.md. However, it omits important behaviors like whether source files are moved/copied, overwrite semantics, what happens if sync fails, or any permission 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 two sentences, front-loaded with the core purpose, and contains no redundant information. It is efficient and well-structured.

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?

For a tool with 5 parameters and no output schema, the description covers the primary flow but lacks details on return values, error handling (e.g., missing filenames), and edge cases like simultaneous use of local_dir and sync_to_mac. The overall context is adequate but not fully complete.

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 100%, so baseline is 3. The description adds minimal value beyond the schema, only reinforcing the default sync destination and notes file. It does not clarify parameter interdependencies like local_dir vs sync_to_mac or folder_name constraints beyond what schema already states.

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 the action: curate selected ComfyUI output images into a named folder on spark and sync to the Mac by default, with optional NOTES.md. It distinguishes from siblings like view_image and list_outputs by focusing on copying/curating rather than viewing/listing, though it does not explicitly name alternatives.

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?

Usage context is implied: use this tool to select and save output images to a folder. However, there is no explicit statement of when to use it over siblings or when not to use it, and no exclusions or alternative tool references.

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