create_single_slide

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

Discloses async behavior (returns job ID, poll check_job_status), typical completion time (20-40 seconds), and faster-than-full-deck nature. No annotations provided, so description carries full burden and does well.

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 sentences, front-loaded with purpose, no redundant words. Every sentence adds value: purpose, use cases, sibling alternative, async mechanics, and speed comparison.

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?

Covers purpose, usage, async behavior, polling instruction, timing, and sibling distinction. Without output schema, description appropriately explains what to expect (job ID) and how to use it. Complete for the tool's complexity.

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 parameters thoroughly. Description adds context about return value (job ID) but does not add new parameter-specific semantics beyond schema. 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?

Clear verb 'Generate' and specific resource 'a single AI-designed slide from a topic'. Lists use cases (hero slides, social-media graphics, one-off visuals) and distinguishes from sibling tool create_presentation_from_topic for multi-slide decks.

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 states when to use (hero slides, social-media graphics, one-off visuals) and when not (full multi-slide deck, directing to create_presentation_from_topic). Clear guidance.

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