Create deck from outline

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive, open-world write, and the description adds the bulk/atomic 'one call' framing. However, the layout defaults it cites are already stated verbatim in the schema's layout field, and it says nothing about repeat-invocation behavior (duplicate decks), permission requirements, or partial-failure semantics — notable for a batch mutation.

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?

Three short sentences, front-loaded with the action and scope, followed by default behavior and routing advice. No filler or restatement of the tool name.

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 bulk creation tool with no output schema and 22 siblings, the description omits what the call returns (deck/presentation identifier or URL) — information an agent needs to actually 'refine with other tools'. Themes, fonts, and slide structure are adequately implied, but the handoff context 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 description coverage is 100%, including the theme enum, layout enum, and nested slide fields, so the schema carries parameter meaning on its own. The description adds only the outline shape at a high level and repeats the layout default, so baseline 3 applies.

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 states a specific verb (create), a concrete resource (a themed Google Slides deck), and the input form (a structured outline), plus 'in one call' which separates it from the single-slide/single-element siblings like add_slide or create_presentation. An agent can tell exactly what this produces without opening the schema.

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?

'Use this for most new decks, then refine with other tools' gives an explicit default recommendation and signals the follow-up pattern (bulk create, then granular edits). It stops short of naming which sibling to use for refinement or when to prefer create_presentation instead.

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