duplicate_slide

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

No annotations, so description covers key behaviors: exact copy, insertion position, return of new ID, and required OAuth scope. Lacks mention of potential side effects like auto-save, but generally transparent.

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?

Efficient 8-sentence structure, front-loaded with main purpose, each sentence adds distinct value. No redundant or vague language.

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?

Covers core functionality, limitations, chaining, alternatives, and auth. Lacks error handling details, but overall sufficient for agent invocation.

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?

Adds meaning beyond schema: explains page_object_id can be slide or element with examples, and clarifies cloning behavior. Schema has 67% coverage; description fills gaps for the undocumented parameter and adds context for others.

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?

Clearly states duplicate slide or page element within a presentation, specific verb and resource. Distinguishes from siblings like copy_drive_file and mentions chaining with reorder_slides.

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?

Explicitly says when to use (exact copy, same presentation), when not to (different presentation), and provides alternatives. Also notes limitation of one object per call and loop for many.

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