Synchronize an approved Personal Gallery

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

Adds meaningful behavioral context beyond annotations: dryRun defaults true, applying imports approved entries, skips drafts, and logically archives archived entries. This is consistent with idempotentHint=true and destructiveHint=false, and provides concrete filtering logic.

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 concise sentences front-load the core purpose and then add critical behavioral detail. No wasted words; every sentence earns its place.

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 synchronization tool with 8 optional parameters and combined plan/apply behavior, the description is too thin. It lacks details about the relationship between planning and applying, return values, error conditions, or how 'stable imports' are achieved. The output schema helps but the description does not sufficiently cover the tool's complexity.

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?

With schema coverage at only 13%, the description partially compensates by explaining dryRun's default and the reviewStatus-driven behavior (approved/draft/archived). However, it does not elaborate on language, assetKind, codeStatus, plotFamily, sourceCommit, or galleryDirectory beyond the schema's own note.

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 it validates a Gallery and plans stable imports, then explains the apply behavior (imports approved, skips drafts, archives archived). This distinguishes it as a sync tool that combines planning and applying, unlike sibling tools like plan_import or apply_import.

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 implies usage for gallery synchronization, mentioning dryRun and apply behavior, but does not explicitly contrast with sibling tools like plan_import or apply_import. There is no when-not-to-use guidance or alternative recommendations.

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