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

With annotations already covering safety (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description goes well beyond them: it discloses what is preserved (blocks, translations, background, speaker notes, with the notes caveat tied to edit permission), how internal links are rewritten, and that dangling links lead nowhere across presentations. It also states the return shape (ids only unless response is "full"), which is exactly the behavioral context an agent needs before invoking a mutating copy.

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?

Front-loaded with the action and mode split, then the preservation and link semantics, then placement defaults, then the return contract — a sensible order with little filler. The dense link-rewriting sentence is hard to parse and would read better as separate clauses, but overall length is proportionate to the operation's complexity.

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 six-parameter copy tool with a full input schema and an output schema, everything an agent needs is present: scope, permission caveat on speaker notes, placement defaults, multiplicity semantics, link behavior, and return detail. Return values need not be re-explained given the output schema, and the description does not attempt to.

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 100%, so baseline is 3, but the description adds real meaning on top: "copies" is explained as repeated duplication in turn (one prepared slide for each appendix) and "after" is given its default resolution for both the duplicate and cross-presentation cases, which the schema does not state. Enumerable "response" is only summarized, not enriched.

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 first sentence states a specific verb (copy) and resource (slides with all their blocks) and immediately splits the operation into two distinct modes: duplicating within this presentation versus copying from another. It does not name the neighboring siblings (add_slides, reorder_slides, add_slide) that an agent might confuse it with, so sibling differentiation is implied rather than explicit.

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?

"slide_ids" of this very presentation (to duplicate them) or of the presentation "from" (any you can see)" clearly maps each scenario to the relevant parameter, and the default placement rules are spelled out for both modes. What is missing is an explicit exclusion or alternates clause, e.g. when to use add_slides instead when the goal is new content rather than a copy.

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