add_slide

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

Annotations provide only a title and no read-only or destructive hints, so the description carries the burden of behavioral disclosure. It confirms the operation adds a slide but does not explain side effects, default behavior, what happens to the existing presentation, or whether background styling applies only to the new slide.

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 a single concise sentence with no filler words. It is front-loaded with the main action, though it omits valuable detail that could be added without excessive length.

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?

Despite having an output schema, the tool has 7 parameters, zero schema descriptions, and a large set of similar sibling tools. The description is too sparse to provide complete context for correct invocation, especially regarding required context like which presentation to modify and how layout/background choices behave.

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%, and the description barely compensates. It vaguely references 'background styling' but does not explain the individual parameters like title, layout_index, presentation_id, color_scheme, background_colors, or gradient_direction, nor their expected formats or defaults.

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 ('Add a new slide') and the resource ('the presentation'), with a specific mention of optional background styling. It does not explicitly differentiate from sibling tools like create_slide_from_template or apply_slide_template, but the core purpose is unambiguous.

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 tool versus alternatives such as create_slide_from_template, apply_slide_template, or duplicate_slide. The description does not state prerequisites, intended use cases, or situations where another sibling tool would be more appropriate.

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