generate_social_teaser_image

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

No annotations provided, so description carries full burden. It mentions auto-selecting aspect ratio and returning a queued media job, which are behavioral. But it does not disclose idempotency, side effects, or permissions. Adequate but not rich.

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?

Description is fairly concise with five sentences, front-loaded with purpose and key behaviors. Some repetition (e.g., multiple examples of usage) but no unnecessary detail. Well-structured.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description covers purpose and return type (queued media job) but lacks details on error handling, prerequisites, or how to process the queued job. Could be more complete given 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 coverage is 100%, so baseline is 3. Description adds marginal context by listing some parameters (title, summary, tone, brand_style) and mentioning auto-selection of aspect ratio, but does not significantly enhance understanding beyond the schema.

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?

Description clearly states the tool creates social media teaser images for specific platforms, with auto aspect ratio selection. The verb 'create' and resource 'social media teaser image' are explicit, and it distinguishes from sibling tools like generate_article_hero_image.

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?

Description provides clear context for when to use: for social graphics, shareable images, post visuals, or og:image alternatives. However, it lacks explicit exclusions or comparisons to sibling tools like generate_article_hero_image, so not a 5.

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