Explicitly upsert a Gallery or Transfer Package source

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

The description adds valuable behavioral context beyond the annotations: 'atomically replace' indicates atomicity, 'one stable snapshot' limits scope, and 'Code is copied but never executed' is a critical safety disclosure. These traits are not present in the annotations, and the description does not contradict them.

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 long, front-loaded with the primary purpose, followed by usage guidance and a critical safety note. Every sentence contributes meaning, with no repetition or filler.

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 an output schema present and annotations covering idempotency and safety, the description provides the essential purpose, usage context, and a key behavioral note. It does not elaborate on failure modes or replacement semantics, but these are largely covered by the structured fields.

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?

The schema provides no descriptions (0% coverage), so the description must compensate. It mentions the concepts of Gallery/Transfer Package and snapshot, giving some context for galleryPath and packagePath, and sourceCommit is implied. However, it does not explicitly explain each parameter's role or format, leaving room for ambiguity.

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 tool's action: 'Validate and create or atomically replace one stable Gallery/Transfer Package snapshot.' It includes a specific verb (upsert), resource (Gallery/Transfer Package snapshot), and distinguishes itself by referencing figure_library_diff for content changes. The additional note that 'Code is copied but never executed' further clarifies the tool's role.

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 description explicitly instructs 'Use figure_library_diff first when content changed,' naming an alternative tool and the condition under which it should be used instead. This provides clear guidance on when this upsert tool is appropriate, distinguishing it from related sibling tools.

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