document.paste

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

With no annotations, the description carries the behavioral burden and does so for key traits: every pasted shape receives a new id and is displaced by (offset, offset) pt so repeated pastes cascade. It omits edge behavior such as what happens when the clipboard is empty or holds non-shape data, and gives no indication of what the call returns.

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 compact sentences, front-loaded with the action and followed by the non-obvious cascade behavior. Nothing is redundant or padded.

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 simple two-parameter mutation with no annotations and no output schema, the description covers action, target selection, and placement behavior. The main residual gap is return information (e.g., ids of newly pasted shapes) and error conditions, which no other field supplies.

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 only 50% (slide_index has no description), but the description compensates: it explains that offset is applied on both axes relative to the original and that the target slide can be the current one or an explicitly specified one. That is meaningful semantics beyond the bare schema fields.

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?

States a specific verb and resource ('Paste shapes from the clipboard') plus the target ('current or specified slide'). The explicit 'shapes' resource distinguishes it from the sibling document.paste_slide, which handles slides rather than shapes.

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 implied by 'from the clipboard' — an agent can infer it should follow document.copy/document.cut and that clipboard.peek can verify contents — but no alternative or when-not condition is stated explicitly (e.g., versus document.duplicate or paste_slide).

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