Set slide background

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

Annotations already declare this is a write (readOnlyHint=false) but not destructive, and the description is consistent with that. It adds one useful scope signal — only solid colors, not gradients or images — but says nothing about whether an existing background is overwritten, whether layout/master backgrounds are affected, or what is returned.

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 zero redundancy. The action and the resource appear immediately, and every word carries information.

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 low-complexity, 3-parameter mutation with full schema coverage and non-destructive annotations, the definition is adequate but bare: it omits overwrite behavior and return shape. Nothing needed to call it correctly is missing, but the agent gets no runtime expectations.

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 100%, so all three parameters (presentationId, slideId, color with a hex example) are already documented in the schema. The description's only contribution is the word "solid," which mildly reinforces the color format; baseline 3 applies.

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 pairs a specific verb ("Set") with a specific resource ("a slide's background") and constrains the value type ("solid color"). It is unambiguous, though it never names a sibling or notes that no other tool touches backgrounds, so differentiation is only implicit.

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?

There is no guidance on when to use this versus the other slide-mutation tools (move_slide, delete_slide, batch_update), and no mention that background is a presentation-wide-affecting, per-slide property. The agent must infer usage entirely from the name.

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