Export palette component

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's write-to-filesystem behavior is consistent. The description adds specific behavioral context by explaining the effect (the .tox appears in the Palette browser), which goes beyond the annotations. It doesn't mention overwrite risks, but the annotations carry the safety burden.

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 that states action, resource, destination, and benefit without unnecessary words. Every phrase 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 simple tool with full schema coverage and annotations, the description provides enough context to understand the action and outcome. It doesn't describe return values or error cases, but no output schema is provided and the tool's behavior is straightforward.

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 coverage is 100%, with all parameters described in the schema. The description adds minimal parameter-specific meaning, only reinforcing 'native Palette folder' which relates to palette_dir. Baseline 3 is appropriate since the schema does the heavy lifting.

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 uses a specific verb ('Save') with a clear resource (COMP) and output (.tox), and specifies the destination (native Palette folder) and purpose (appears in Palette browser for drag-and-drop reuse). This clearly distinguishes it from siblings like export_look_tox or save_component_to_vault.

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 strong usage context: it should be used when you want a COMP to become a reusable palette component. It doesn't explicitly name alternatives or exclusions, but the context is clear and distinct from sibling tools.

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