keynote_set_slide_background

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

No annotations are provided, so the description must disclose all behavioral traits. It only states the basic action without mentioning side effects (e.g., overwriting existing background, undo capabilities, permission requirements). The description is insufficient for a mutation tool.

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?

Extremely concise: two sentences, no unnecessary words. The purpose and use case are front-loaded. Every sentence contributes meaning.

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 no output schema and annotations, the description should cover what happens after the tool runs (e.g., immediate visual change). It only states the action and a use case, leaving out completeness about behavior and return value.

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?

Input schema has 100% coverage, with clear descriptions for all three parameters. The description adds no extra meaning beyond the schema, adhering to the baseline of 3.

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 changes the slide background to a solid color, specifying 'solid color' which differentiates it from gradients or images. However, it does not explicitly differentiate from siblings like keynote_set_element_fill_color, but the resource is clearly the slide background.

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?

Provides a use case: 'establish a consistent color palette across all slides.' This gives some context for when to use, but lacks explicit when-not-to-use or alternatives. No mention of prerequisites or restrictions.

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