List Backdraw reference collections

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered; the description adds genuinely new behavior by describing the return shape and ordering ('each with its image count, folder and files (newest first, with the site they came from)'). The only omission is any note on collection count/volume limits, which is minor for a zero-parameter listing tool.

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 sentences, purpose front-loaded, with the Chrome/right-click parenthetical explaining provenance rather than padding. The nested parentheses ('(right-click an image, "Add to Backdraw")' and '(up to 16 references; reference_files picks specific ones)') are dense but each carries real constraint information.

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?

There is no output schema, so the description must convey return values itself — and it does, listing per-collection fields, ordering, and the source-site detail. Combined with the annotations covering read-only/closed-world and the schema being empty, an agent has everything needed to call this and use the result.

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?

Zero input parameters, so the baseline is 4 and there is nothing in the schema to contradict. The description still adds downstream semantics by explaining that a returned collection name becomes generate_image's reference_collection value, tying the output to another tool's parameter.

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?

Specific verb + resource ('List the reference collections the user saved in Chrome') with the origin of that data spelled out (right-click an image, 'Add to Backdraw'), so an agent knows exactly what corpus this covers. It also enumerates the fields returned per collection (image count, folder, files newest first, source site), which separates it cleanly from list_projects and the job tools.

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 explicitly routes the agent forward: 'Pass a collection's name as generate_image's reference_collection to attach its images (up to 16 references; reference_files picks specific ones).' That names the sibling tool, the parameter to feed, and the alternative path for a subset of files. It stops short of stating when not to call this (e.g. when the user already named a collection), so it is clear context rather than full when/when-not guidance.

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