Create Presentation

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

Annotations already convey that this is a write operation (readOnlyHint=false, idempotentHint=false). The description adds no extra behavioral context such as where the presentation is created, whether it creates a file in Google Drive, or any side effects. With no additional context, it does not go beyond what annotations already provide.

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 a single, concise sentence that directly states the action and target. There is no unnecessary fluff or repetition. Every word adds value, making it highly efficient.

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 simple tool with just two parameters, a complete schema, and an output schema, the description is largely sufficient. It could mention that created presentations are empty or saved to the user's Drive, but the current information combined with schema and annotations provides enough context for this straightforward operation.

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 fully describes both parameters (title and user_google_email) with 100% coverage. The description itself adds no parameter-specific meaning beyond the schema. This aligns with the baseline of 3 when the schema carries the load.

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 the verb 'Create' and the specific resource 'a new Google Slides presentation.' This distinguishes it from sibling tools like import_to_google_slides (which imports) and create_drive_file (which creates generic files). The purpose is unambiguous.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or how it differs from related tools like import_to_google_slides. The description is purely definitional and offers no context for selection.

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