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

The description discloses multiple behavioral traits beyond the annotations: it always creates a NEW deck, it cannot modify user-owned decks due to scope, it gracefully handles expired ad-library links (embeds text instead and reports count), and it returns a presentation id + URL. Annotations only provide binary hints; this description enriches the agent's mental model substantially.

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 somewhat lengthy but each sentence earns its place: the first states the core purpose, the second gives marketing context, the third explains the new-deck limitation, the fourth covers the expired-link edge case, and the fifth states the connection requirement. It is well-structured and front-loaded, though a sentence or two could be trimmed without losing information.

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 complex tool that creates Google Slides decks, the description covers the return value (presentation id + URL), the behavioral edge cases (expired links, new-deck only), and the prerequisite (Drive connected). No output schema exists, so the description carries the full burden of explaining what the agent receives, and it does so completely.

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% and each parameter has a description in the schema (limit range/default, title default, collection by name/id). The tool description restates these facts without adding new meaning beyond what the schema already provides, so it stays at the baseline 3.

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 opens with a specific verb and resource ('Turn a SWIPEFILE COLLECTION into a real Google Slides deck') and enumerates exactly what each slide carries (creative, brand, copy, run dates, platform). It also contrasts with the prior JSON-only export, making the tool's distinct value clear against siblings like save_to_drive and update_drive_file.

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?

It clearly frames when to use this tool—for presenting a collection to a client/team, contrasting with the old JSON export—and warns that it cannot touch existing decks due to the drive.file scope, implying when not to use it. It also states the prerequisite (Google Drive connected). It does not name a specific alternative tool, but the context is strong enough for an agent to decide.

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