set_slides_background

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

With no annotations provided, the description carries the full burden. It discloses the write nature (OAuth scope) and the important behavior of overriding inherited master/layout backgrounds with a solid color. However, it does not mention reversibility, side effects on other slide properties, or error conditions, which would elevate it to a 5.

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 extremely concise: three sentences, each serving a distinct purpose. The first sentence is the action, second distinguishes from alternatives, third covers usage pattern and key behavior. No fluff, well front-loaded.

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?

Given the tool's simplicity and the presence of an output schema, the description covers purpose, alternatives, usage pattern, OAuth scope, and key behavioral trait. It is complete enough for an agent to use correctly, but lacks error handling or edge case details that would make it a 5.

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 80%, so the baseline is 3. The description does not add any parameter-specific semantics beyond what the schema already provides (e.g., for color, alpha, page_object_id). The `user_google_email` parameter lacks schema description and is not elaborated in the description, meaning the description adds no extra value for parameters.

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 action: 'Set the background fill color of a single slide' with the verb 'set' and resource 'background fill color'. It distinguishes from shape styling by noting it affects the page itself, not a shape, and explicitly names the sibling tool `style_slides_shape`. This provides high specificity and differentiation.

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 provides an alternative tool for shape fills (`style_slides_shape`) and instructs to call this tool once per slide for multiple slides. It also documents the required OAuth scope, giving clear when-to-use and what-not-to-use guidance.

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