create_presentation

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

No annotations are provided, so the description must fully disclose behavior. It only states it creates a presentation and optionally accepts a theme. It omits critical details like whether the presentation is saved, how to reference it later, or any side effects. The description is too sparse for a creation tool.

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 sentences with no wasted words. It efficiently conveys the core action and optional parameter. Could be slightly improved by front-loading the result, but overall concise.

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?

The description is very basic. It doesn't explain what 'blank' means, what happens to existing presentations, or how to access the new presentation. Given the lack of output schema and the complexity of Keynote workflows, this is incomplete. A user would need to infer behavior from sibling tools.

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?

The input schema has 100% coverage with a clear description for themeName. The description adds 'Optionally specify a theme name' which matches the schema. Schema handles semantics well, so description provides minimal additional value. Baseline 3 is appropriate.

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 clearly states it creates a new blank Keynote presentation. This is specific and distinguishes from sibling tools like open_presentation or apply_theme.

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?

The description implies usage when a new presentation is needed but provides no guidance on when not to use it or how it compares to alternatives like design_from_template or apply_theme. No explicit context for selection.

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