set_shape_palette

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

No annotations are provided, so the description carries the full burden. 'Embed local shape assets' hints at a mutation that writes assets into the workbook, but nothing is said about overwriting an existing palette, required permissions, or what happens to previously mapped members.

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 compact sentence with no filler, and the core operation is front-loaded. It is efficient, though the economy comes partly at the cost of the missing detail noted elsewhere.

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?

A mutation tool with no annotations, zero schema descriptions, and a nested object parameter needs substantially more than one sentence. The output schema is present, so return values need not be covered, but input formats and side effects remain undocumented.

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% across 3 parameters. The description loosely gestures at 'categorical members' (field), shape assets (shapes), and 'native palette' (palette), but gives no format for the field name, the shape-value mapping object, or valid palette names.

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 verb+resource ('set_shape_palette') is stated, but the sentence mixes two operations ('embed local shape assets' and 'map categorical members to the native palette') without clarifying which this tool actually performs, and 'native palette' blurs the line with the color-palette sibling set_compound_color_palette.

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?

No when-to-use guidance, no prerequisites, and no mention of the closely related set_compound_color_palette or when to pick shapes over colors. The agent must infer all routing from the name alone.

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