document.paste_slide

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

With no annotations, the description carries the full burden. It does disclose useful behavior — default placement at the last slide and one command per pasted slide so undo removes them cleanly — but omits what happens when the clipboard is empty, whether existing slides shift, and whether the paste is undoable as a group or individually.

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?

Two sentences, front-loaded with the core action and its default, followed by a relevant undo note. No wasted wording.

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 one-optional-parameter, no-output-schema tool, the description covers placement default and undo granularity adequately. Only the failure mode for an empty/incompatible clipboard is missing.

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 coverage is 0% for the single parameter, so the description must compensate. It does add the default ('last slide') and the positional meaning of 'after', but leaves index base (0- vs 1-based) and valid range unspecified.

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?

Specific verb+resource: 'Paste slides from the slide-level clipboard', which distinguishes it from document.paste (generic clipboard paste) among the siblings. It does not explicitly name the alternative tool or contrast conditions, but the scope 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?

Usage is only implied: the mention of a 'slide-level clipboard' suggests document.copy_slide must have populated it first, and 'after after_index' implies inserting into an existing deck. No explicit when-to-use/when-not or prerequisites (e.g., empty-clipboard behavior) are stated.

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