generate_slideshow

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

No annotations provided, so description carries full burden. Discloses: consumes one slideshow from monthly cap, not idempotent, takes 30-120 seconds, returns slideshow_id and download_url valid 24h, delivery failures don't fail generation, requires ready profile. Lacks explicit mention of errors beyond 'rejected' for unknown preset_id. Still very comprehensive.

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 well-structured paragraph with no wasted words. Core function is front-loaded, followed by usage rules, timing, return info, and error handling. Every sentence adds value.

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?

Despite no output schema and 5 parameters, the description covers the return values (slideshow_id, download_url), side effects (consumes cap, not idempotent), prerequisites (ready profile), error handling (delivery failure reason, unknown preset_id rejected), and timing. 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 baseline is 3. Description adds value beyond schema: explains profile as source of truth, hook becomes slide 1 and post title, preset defaults, deliver options and their effects, tiktok_account_id as confirmation. Adds context like 'often the top result from generate_hooks'.

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 'Generate ONE complete TikTok slideshow from a Svmmon profile and a hook, render it, and optionally deliver it to TikTok or Telegram.' The verb (generate) and resource (slideshow) are specific. It distinguishes from siblings like generate_hooks (hooks) and get_slideshow (retrieval).

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 says when to use: 'Use when the user asks to make/create/build a slideshow or post from a hook.' Provides when-not: 'never call it twice for the same request', 'if it times out, check list_slideshows before retrying'. References siblings: list_profiles for ready profiles, get_usage for cap checking.

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