auto_generate_presentation

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

No behavioral annotations are provided beyond a title, so the description carries full responsibility for disclosing side effects. It says 'automatically generate' but does not clarify whether this creates a new presentation, overwrites the current/original content, requires authentication, or has other notable behaviors. The 'uses current if None' note on presentation_id gives some context but not enough for a potentially destructive operation.

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 front-loaded with a single-sentence purpose followed by a structured Args list. It is reasonably concise and every parameter line adds meaning beyond the bare schema, though listing all parameters inline makes it slightly longer than an ideal standalone usage summary.

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?

Given the tool's complexity, zero schema descriptions, and no safety annotations, the description covers the obvious need: generating a presentation from a topic with preferences. But it omits guidance on choosing this tool over siblings and does not explain the mutation/overwrite behavior, which is essential for safe 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?

Schema description coverage is 0%, so the description must and does compensate. It explains all seven parameters, including slide_count range, presentation_type allowed values, inclusion booleans, and the presentation_id fallback behavior. However, 'color_scheme: Color scheme to use' is not very informative about accepted values, leaving some ambiguity.

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 clear action and object: 'Automatically generate a presentation based on topic and preferences.' This distinguishes it from manual creation tools and template-based siblings by emphasizing automatic generation from a topic, though it does not explicitly name alternatives or edge cases.

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 use when a presentation should be automatically generated from a topic and options. However, it does not provide explicit 'when to use vs alternatives' or 'when not to use' guidance, and the large sibling list of create_presentation, create_from_template, and slide tools makes this gap meaningful.

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