add_to_catalog

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses that duplicates are skipped, which is real behavior an agent otherwise could not know, but it omits whether the target catalog must already exist, whether it errors or creates one, and what permissions or side effects apply to a mutation.

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?

A single front-loaded sentence with the core action first and the one behavioral caveat parenthesized. Nothing is wasted or padded.

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?

The output schema exists, so return values needn't be explained. However, for a mutation tool with zero annotations and zero schema descriptions, the description leaves key caller questions unanswered — must the catalog pre-exist, what happens to invalid paths, and what the catalog name refers to.

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% for both parameters, so the description must compensate. 'catalog' loosely implies the `name` parameter and 'image files' loosely implies `paths`, but it never clarifies that `name` is a catalog identifier (created via create_catalog) or whether `paths` accepts absolute file paths, directories, or URLs.

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 and resource: adding image files into a named gThumb catalog. It is readily distinguishable from siblings like create_catalog and remove_from_catalog by the verb, though the description never names those alternatives explicitly.

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 is implied by the verb phrase 'add image files to a catalog' — no explicit when-to-use, when-not-to-use, or named alternative is given. The duplicate-skipping note hints at preconditions (items already present) but does not guide tool selection.

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