render_slides

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it supports Gemini-generated visuals (customSvg, customImageUrl), mentions platform-specific output formats, and advises checking for brand kits. However, it doesn't cover potential side effects like file system changes or error conditions.

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 well-structured with clear sections (purpose, usage, features, tip, returns) and uses bullet points efficiently. Every sentence adds value, though the 'Tip' section could be integrated more seamlessly. It's appropriately sized for the tool's complexity.

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 (5 parameters, nested objects) and lack of annotations/output schema, the description does a good job covering key aspects: purpose, usage, visual support, and returns. However, it could better address error handling or performance considerations for a rendering tool.

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%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema, mentioning slide plan sources and platform outputs but not elaborating on parameter interactions or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

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 tool's purpose with specific verbs ('render') and resources ('slide plan into SVG + PDF or PNG'), distinguishing it from siblings like preview_slides (which previews) and create_carousel (which may involve different workflows). It explicitly mentions output formats for different platforms.

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 provides explicit guidance on when to call ('After preview_slides when you've reviewed or enhanced the slide plan') and includes alternatives ('Also accepts manually crafted slide plans'). It references sibling tools like list_templates and preview_slides, offering clear context for usage.

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