render_presentation

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

With no annotations, the description carries the behavioral burden and does disclose the key trait: every successful call produces a new immutable version and never overwrites an earlier deck. It omits auth requirements, what happens on a base-version mismatch, and any rate/performance characteristics.

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 operation and its outputs before the parameter-mode guidance. No filler and every sentence carries distinct 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?

An output schema exists, so return values need no explanation, and the versioning model is well covered. What remains thin is the expected shape of the nested 'presentation' object and the failure path when expected_base_version does not match.

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 compensate; it usefully explains project_id (omit for a new project) and expected_base_version (the current version for revisions). The third parameter, the nested 'presentation' IR payload, is left entirely undefined, so compensation is partial.

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?

States a specific verb ('Render'), the precise input ('complete Presentation IR'), and both outputs ('editable PPTX and source bundle'). That output profile cleanly separates it from siblings like validate_presentation and get_presentation_ir without the agent opening any 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?

Explicitly covers the two operating modes: omit project_id for a new project, or pass project_id plus expected_base_version for a revision. It does not mention alternatives or prerequisites (e.g., validate first), so it stops short of the full when/when-not/alternatives bar.

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